| Summary: | Layers docker in 5.0 have wider minimun width compared to 4.x | ||
|---|---|---|---|
| Product: | [Applications] krita | Reporter: | acc4commissions |
| Component: | Dockers | Assignee: | Krita Bugs <krita-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | minor | CC: | ahab.greybeard, griffinvalley, halla |
| Priority: | NOR | ||
| Version: | nightly build (please specify the git hash!) | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | All | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | left 5.0, right 4.4.3 | ||
|
Description
acc4commissions
2021-04-20 13:10:49 UTC
Created attachment 137728 [details]
left 5.0, right 4.4.3
Not here, the two are exactly the size, though 5.0 uses bigger fonts.
For 5.0.0-prealpha vs 4.4.x, I see the Layers docker as the same minimum width. The Advanced Colour Selector minimum width is notably larger in 5.0.0. The standard Animation workspace for 5.0.0 gives a minimum window width of 1507 pixels which is too wide for my 1280 x 1024 monitor. This is because of the increased minimum width of the new Animation Timeline docker combined with the adjacent Onion Skins docker. The 'obvious' workaround is to reposition or remove the Onion Skins docker but that would not be obvious to new users with small width monitors. I'm using Windows with system text display size 125%, and I adjusted it to 100% and layers docker in both Krita 4.x / 5.0 became about the same size. (Actually in 5 it's still bigger by few pixels though.) And I doubt that this variation is intended. Other dockers like Advanced Color Selector, Brush Presets, Channels etc all can be resized smaller enough though. For me it's only Layers docker that has big minimum width. :/ If you can't fix the issue on your side, could you at least make Layers docker a little more slimmer? I found out that setting the Custom Interface Font size in Krita changes minimum widths of dockers and windows. Although the font is crazy small to read if I match 5.0's dockers to 4.x ones by doing this. I am going to close this, as I doubt we're going to see any fixes here until we move away from our current docker system. This is fixed in yesterday's nightly. See, it was not intentional. Anyway I'm glad it's addressed. |