https://bugs.kde.org/show_bug.cgi?id=493498
            Bug ID: 493498
           Summary: Persisting rescaled/positioned window across sessions
    Classification: Applications
           Product: digikam
           Version: 8.5.0
          Platform: Microsoft Windows
                OS: Microsoft Windows
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: digikam-bugs-n...@kde.org
          Reporter: carbonwer...@hotmail.com
  Target Milestone: ---

***

***

SUMMARY
The window size/state button for the main application window does not persist
size or position of partial screen window setup on app restart

STEPS TO REPRODUCE
1.  On app start in Windows, it seem to default to full screen
2. Using the window state button, resize the GUI to be partial screen size at
some random position (mid-screen)
3. Close the app via the X window button.
4. Restart app
5. Select the window size state button again

OBSERVED RESULT
Window size/position state is defaulted to full screen again

EXPECTED RESULT
Window size/position should be persisted, so that on selection of the window
state button, the GUI will change its scale and position to the last
scale/position set in that 'non-full-screen' mode.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
I understand that some OSs do not support this partial window size option (it
is foreground in full screen, or background, or closed). But is is supported in
Digikam- it just isnt persisted across sessions. Having to manually drag a full
screen window is a hassle- where some OSs have the border selection as a single
pixel width, and others (like Windows) put Close or a Taskbar etc adjacent to a
drag corner. So, even if it isnt a universal standard on all OSs, it is hard to
see how persisting this via an ini file would ever be a net negative. Worst
case, perhaps it could be an option setting that defaults to existing behavior
persisted across session restart.

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

Reply via email to