https://bugs.kde.org/show_bug.cgi?id=512876

Branislav Klocok <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|FIXED                       |---
             Status|RESOLVED                    |REOPENED

--- Comment #4 from Branislav Klocok <[email protected]> ---
Reopening -- the fix in 26016db is incomplete. It corrects selecting a page
size directly from the combo, but the page size is still lost in the normal
preview workflow (skanpage/ksanecore 26.04.2, HP LaserJet Pro MFP M26nw
flatbed):

1. Select A4 -- sticks.
2. Run a Preview scan.
3. After the preview completes, "Scan area size" has reverted to Custom and
stays there; on exit it is saved as Custom, so A4 is never remembered across
the normal preview-then-scan workflow.

Root cause: Interface::startPreviewScan() sets br-x/br-y to the maximum (full
bed) for the preview, which switches PageSizeOption to Custom (215.9 mm != A4
210 mm). After the preview, scanIsFinished() restores br-x/br-y via
restoreSavedData(), but the page-size combo is not restored:
optionBottomRight{X,Y}Updated only transitions a named size -> Custom (guarded
by m_currentIndex > 0), never Custom -> named. The named-size re-detection in
PageSizeOption::restoreOptions() is connected only to the optionsReloaded
signal, which restoreSavedData() does not emit. The same happens for any manual
scan-area change (Skanpage::setScanArea).

Suggested fix: re-run the page-size detection after restoring the scan area
(post-preview, and after manual area changes), or have
optionBottomRight*Updated / optionTopLeft*Updated also switch Custom -> named
when the geometry matches a named size.

(Apologies for my earlier "verified fixed" comment -- that test only covered
direct combo selection without a preview.)

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to