Bug 74439 - Remember (and restore) size of Libreoffice dialogues boxes (File/Open etc) , after they are manually resized
Summary: Remember (and restore) size of Libreoffice dialogues boxes (File/Open etc) , ...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
(earliest affected) Master
Hardware: All All
: medium enhancement
Assignee: Not Assigned
: 112504 113487 135295 (view as bug list)
Depends on:
Blocks: Dialog
  Show dependency treegraph
Reported: 2014-02-03 13:16 UTC by Stefan Knorr (astron)
Modified: 2022-11-22 11:29 UTC (History)
7 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Knorr (astron) 2014-02-03 13:16:11 UTC
Many LibreOffice dialogues are now resizable which is great. However, custom sizes of the dialogues are not stored for when the dialogue is opened again. Therefore, all dialogues reopen with the default size.
It would be great to remember the users choices (even across sessions).
Comment 1 tommy27 2014-02-16 07:10:42 UTC
valuable enhancement request.

I add Caolan McNamare to CC list. If I remember correctly he did some work about resizability of dialogs.
Comment 2 Caolán McNamara 2014-02-17 12:20:24 UTC
One potential problem is across versions if new widgets get added to a dialog, then restoring an old size might be too slow. So I guess we'd have to limit restoring a size to a dialog to whichever is larger, the saved size or the optimal one. Hmm, of course if something gets removed from a dialog to make it smaller, then it won't shrink to fit if the user already used that dialog and its older larger size is restored.
Comment 3 Stefan Knorr (astron) 2014-02-17 16:20:42 UTC
(In reply to comment #2)
Idea: version dialogues somehow, and throw away the stored values if they are for an older version of the same dialogue. This would lead to additional developer work. Given how the whole minimum-size-changed scenario is more of a corner case, as dialogues usually only change with major versions (~every half year), I am not sure that work would be justified.
If the version could be changed automatically somehow (git hook..?), then of course it might be a viable option.

Two more (fairly common sense) points:
+ dialogues should never be restored smaller than their (current) minimum
+ when users don't change the size of a dialogue, there is no need to store
  dialogue size information
Comment 4 Andreas 2016-02-21 15:33:16 UTC
What a pity nobody working on this bug. I would myself if I was able to. It's somewhat crazy: On one hand there is a big community working on LibO getting better all the time, on the other hand such a basic think like dialog size remembering not being fixed version by version.
Comment 5 Adolfo Jayme Barrientos 2017-09-20 22:49:23 UTC
*** Bug 112504 has been marked as a duplicate of this bug. ***
Comment 6 tommy27 2017-09-22 05:27:30 UTC
I had some viewpoint exchange with Caolan times ago about this issue related to the autocorrect replacement table.

See: Bug 93042 - autocorrect replacement table dialog doesn't remember size change

feel free to mark that as a DUPE if you think so.

IMHO it would be an improvement to remember the dialog size at least during the same session (and the size could be restored to default when you close LibO and start a new session).
Comment 7 Caolán McNamara 2017-10-28 16:42:08 UTC
*** Bug 113487 has been marked as a duplicate of this bug. ***
Comment 8 Xisco Faulí 2019-11-29 13:27:35 UTC
Changing priority back to 'medium' since the number of duplicates is lower than 5
Comment 9 Timur 2020-07-31 09:31:07 UTC
*** Bug 135295 has been marked as a duplicate of this bug. ***
Comment 10 sdc.blanco 2020-07-31 10:51:36 UTC
(In reply to Timur from comment #9)
> *** Bug 135295 has been marked as a duplicate of this bug. ***
I believe this action is a mistake. Bug 135295 has a critical difference from this bug (as described in bug 135295 comment 2)
Comment 11 Dan Dascalescu 2022-06-17 23:48:25 UTC
* bug 149598
* bug 101285 (which was recently fixed)
Comment 12 kimmywatson 2022-11-22 11:28:02 UTC Comment hidden (spam)
Comment 13 kimmywatson 2022-11-22 11:29:39 UTC Comment hidden (spam)