Bug 499652 - Spectacle program is not remembering its maximized state
Summary: Spectacle program is not remembering its maximized state
Status: CONFIRMED
Alias: None
Product: Spectacle
Classification: Applications
Component: General (show other bugs)
Version: 24.12.2
Platform: Neon Linux
: NOR minor
Target Milestone: ---
Assignee: Noah Davis
URL:
Keywords: junior-jobs
Depends on:
Blocks:
 
Reported: 2025-02-07 16:38 UTC by John
Modified: 2025-04-23 10:25 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John 2025-02-07 16:38:20 UTC
SUMMARY
Spectacle program is not remembering its maximized state

STEPS TO REPRODUCE
1. Boot KDE Neon.
2. Open the Spectacle program.
3. Maximize it.
4. Close it.
5. Open it again.

OBSERVED RESULT
The program doesn't remember that before closing it was maximized.

EXPECTED RESULT
The program should open with the same state it was before being closed, in this case, maximized.
Maybe it's a bit weird to have Spectacle open as maximized, but for the consistency with all the other KDE and non-KDE programs that remember their maximized state and for the cases of screenshot with delay or for recording opening it maximized mode is no problem and I would very much like that this program rember its maximized state too like all the others.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
KDE Plasma Version: 6.2.90
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.1
Kernel Version: 6.8.0-51-generic (64-bit)
Graphics Platform: Wayland

ADDITIONAL INFORMATION
Hardware: Laptop Dell Inspiron 5770 (screen: 17 @ 1080p)
Graphics Processor 1: Mesa Intel® UHD Graphics 620 (main)
Graphics Processor 2: AMD Radeon R5 M465 Series
Comment 1 Justin Zobel 2025-02-10 09:53:57 UTC
Confirmed on git master (6.3.80).
Comment 2 Nate Graham 2025-02-19 18:32:34 UTC
Indeed. This is just a matter of adding KConfig.WindowStateSaver objects to every window that should remember its state.