Bug 461954 - DigiKam 7.9 does not remember last position of window when starting, allways open in a small window in middle of screen
Summary: DigiKam 7.9 does not remember last position of window when starting, allways ...
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Usability-Ergonomy (show other bugs)
Version: 7.9.0
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-11-17 15:37 UTC by Björn
Modified: 2023-05-10 14:35 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Björn 2022-11-17 15:37:19 UTC
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
When starting DigiKam on Microsoft Windows 11 PC it allways starting in small window in middle of screen.
Last tested in version digiKam-7.9.0-20221116T183153-Win64

STEPS TO REPRODUCE
1. Open DigiKam and resize or maximaze app window
2. Close DigiKam
3. Open DigiKam and it does not remember last position of window (open a small window in middle of screen)

OBSERVED RESULT
DigiKam does not remember last position of window, allways open in a small window in middle of screen

EXPECTED RESULT
It should remember last position of window and if it was maximized or not

SOFTWARE/OS VERSIONS
Windows: Windows 11
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
It works and remember window position i version 7.8 but not in any of 7.9 versions included digiKam-7.9.0-20221116T183153-Win64
Comment 1 Peter 2022-11-17 15:44:57 UTC
Duplicate of #460779
Comment 2 Maik Qualmann 2022-11-17 15:53:03 UTC

*** This bug has been marked as a duplicate of bug 460779 ***
Comment 3 caulier.gilles 2023-05-10 14:35:50 UTC
fixed with bug 460779