Inkscape master: Sometimes panels load rolled up
<!-- See our full bug reporting guidelines at https://inkscape.org/contribute/report-bugs/ Writing a good bug report will ensure we'll be able to help efficiently. 🙂 --> #### Summary: <!-- Summarize the issue/suggestion concisely: --> Sometimes dialog panels load with the top panels rolled up. Inkscape should remember the ratio of the panel in the vertical space, and load that back no matter the window size. Regression from 1.4. ![螢幕截圖_20250324_183722](/uploads/bddfec87a983c22eaee5c1d277da9c87/螢幕截圖_20250324_183722.png) #### Steps to reproduce: <!-- Describe what you did (step-by-step) so we can reproduce: --> N/A #### What happened? Top part of the panels are rolled up. #### What should have happened? The ratio is remembered. Sample attachments: <!-- Attach the sample file(s) highlighting the issue, if appropriate. --> #### Version info <!-- Open 'Help > About' and click on the little bug icon in the bottom right corner that copies the debug information to your clipboard. For command line users, run 'inkscape --debug-info'. For Inkscape 1.0.2 and older, please manually add the Inkscape Version and Operating System Version. The Inkscape version is listed in the About dialog. For command line users, run 'inkscape -V' Paste the information in the empty space between the apostrophes below: --> ``` Inkscape 1.5-dev (fab112cff8, 2025-03-17, custom) Compile (Run) GLib version: 2.84.0 GTK version: 4.18.2 (4.18.2) glibmm version: 2.84.0 gtkmm version: 4.16.0 libxml2 version: 2.13.6 libxslt version: 1.1.43 Cairo version: 1.18.4 (1.18.4) Pango version: 1.56.3 (1.56.3) HarfBuzz version: 10.4.0 (10.4.0) Poppler version: 25.03.0 OS version: Slackware 15.0 x86_64 (post 15.0 -current) ``` <!-- ❤️ Thank you for filling in a new bug report, we appreciate the help! ❤️ Please be patient while we try to find the time to look into your issue. Remember that Inkscape is developed by volunteers in their spare time, we'll try our best to respond to all reports. --> <!-- Please be careful when/after writing # for example in logs, code, or versions of linux - use inline code span - single backticks (`) before and after it, like this - `#1618` - use multi-line code block - triple backticks (```) to fence/enclose console logs - attach long logs as a text file. -->
issue