With a fresh profile, modules start maximized. That's not a good window size for large screens, so users have to resize. Doing this with Calc ends up in a tiny and hard to spot square (title bar only). We should a) use a default windows size according the OS and b) at least define a minimum size for Calc. AFAIR, it's not an issue for other modules.
Thank you for reporting this. I confirm it with:
Build ID: 77ae0abe21f672cf4b7d2e069f1d40d20edc49a7
CPU threads: 4; OS: Linux 4.9; UI render: default; VCL: gtk3;
TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-05-31_15:33:33
Locale: en-GB (en_GB.utf8); UI-Language: en-US
When minimizing it the window size changes to really tiny square around 12px.
Regarding starting as maximized I don't see it as an issue because the window size will be preserved for the next start. User will only have to change it once and most people don't have large screens.
Since Xisco requests input from UX, let's talk about. I work on a large super-wide screen where the modules are set to the maximum screen size - makes not much sense and I always resize first to ~1600x1200px, which is a 4/3 ratio.
At least Windows has a application size policy with PreferredLaunchViewSize and we should follow this.
Last but not least we define as minimum required resolution 1280x768px in , that could also be taken into account.
Of course, the actual value has to be responsive to the resolution, and the default scaling should work with HiRes too (8k screens might come in some years). And we should maximize in case of very small screens.
We discussed the topic in the design meeting and agreed on the proposal, considering a 16:9 ration, which is better suited for movies, and less space such as 50%, which would be too small. Any minimum value is an advantage over the zero size that might appear to users as broken (therefore I raise the importance).
SetMinOutputSizePixel() is implemented for include/vcl/syswindow and include/sfx2/dockwin but not include/vcl/window.hxx. And this function should receive the actual value from the OS/DE. Probably an easy hack for more experienced developers. Thanks jmux for the code pointers.
@Caolán, I thought you might be interested in this issue...
SetMinOutputSizePixel sets the minimum size below which a window cannot be shrunk, which is probably not whats wanted.
In my case I had the window with 2 mm wight and 1 cm height. It is very hard to notice that this is a window. You can not edit in Calc in 0,02*1 cm... So, a default minim of 4 cm * 4 cm, or maybe 3*3 cm could be done. From my POV a 3*3 cm would be a minimum, else you can not see any cell in any file.
*** Bug 136655 has been marked as a duplicate of this bug. ***
*** Bug 136662 has been marked as a duplicate of this bug. ***