Bug 91557 - FEATURE REQUEST: change Settings dialog window size
Summary: FEATURE REQUEST: change Settings dialog window size
Status: RESOLVED DUPLICATE of bug 91556
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
(earliest affected)
Hardware: All All
: medium enhancement
Assignee: Not Assigned
Depends on:
Reported: 2015-05-24 03:16 UTC by Edmund Laugasson
Modified: 2015-05-24 20:44 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

example view of Settings window with 400% size (87.36 KB, image/png)
2015-05-24 03:16 UTC, Edmund Laugasson

Note You need to log in before you can comment on or make changes to this bug.
Description Edmund Laugasson 2015-05-24 03:16:08 UTC
Created attachment 115926 [details]
example view of Settings window with 400% size

Using 64-bit Linux Mint Cinnamon 17.1 with 4.0.4-040004-generic kernel
LibreOffice version:
Build ID: 0a16c3dda4150008d9be6f24cbd15ac198d116d3
Locale: et-EE (et_EE.UTF-8)

Also the problem is to change Settings dialog window size. If I could change the Settings window size then I could also possibly see the scale factor setting and switch it back to normal.

So the second proposal would be to make possible to change Settings dialog window size and also window splitting position dynamically. Currently there is plenty space on left side but I cannot change the splitting position for now.

As seen on the example image - the Settings window with 400% has plenty of space but cannot change the split position or window size and therefore not possible to see if I could change scale factor back to normal what someone accidentally or intentionally changed too high (400% is the maximum currently).

If there will be not regular buttons on the right top corner then at least there should be possible to drag the window size larger and also drag the split position freely.
Comment 1 Cor Nouws 2015-05-24 20:44:12 UTC
Hi Edmund,

I think if 91556, and the follow ups, are done, this one is superfluous.
So I mark it as dup.

*** This bug has been marked as a duplicate of bug 91556 ***