Bug 357738 - Item // Edit Geolocation window does not remember its size
Summary: Item // Edit Geolocation window does not remember its size
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Plugin-Generic-GeolocationEdit (show other bugs)
Version: 5.0.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-09 15:27 UTC by Milan Knížek
Modified: 2016-01-12 07:07 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Milan Knížek 2016-01-09 15:27:59 UTC
Choosing menu Item // Edit Geolocation opens a new window in the middle of the screen. The window does not have "minimise", "maximise" buttons in the window frame, although manual resizing is possible.

After closing the window and opening it again, the window is sized and located the same as before.

Proposal: add basic "mix", "max" buttons to the top bar of window frame and set the frame to remember its last position.
Comment 1 caulier.gilles 2016-01-09 16:46:31 UTC
The problem is know.

Maik has fixed the problem for 5.0.0-beta3, at least for Setup dialog, as i remember. I don't know for other dialogs.

Gilles Caulier
Comment 2 Maik Qualmann 2016-01-09 18:17:30 UTC
Yes, restore window size should for all dialogs is fixed with digiKam-5.0.0-beta3 (except Kipi-plugins). My Geolocation-dialog has min / max buttons. The last position of the window is not saved, I think it was no different with digiKam4.

Maik
Comment 3 Milan Knížek 2016-01-10 08:14:22 UTC
Ok.

Since it is not clear from your answers, I hope that if not position, then at least the size of the Geolocation-dialog window is remembered. It would help the user to save a mouse-click every time opening the dialog.
Comment 4 Maik Qualmann 2016-01-12 07:07:45 UTC
Yes, the Geolocation window remembers the window size in digiKam-5.0.0-beta3. I think we can close this bug.

Maik