Created attachment 171737 [details] A video depicting the issues SUMMARY After updating KDE frameworks to the version 6.4.0 I've encountered several issues with desktop icons STEPS TO REPRODUCE 1. Create a shotcut on the desktop with a name that doesn't fit in one line 2. Try to open it after hovering cursor over it and then moving the cursor away 3. Try to drag the icon across the screen OBSERVED RESULT 1. The name doesn't fit in the highlighted frame 2. The shortcut doesn't open with repeated clicks 3. Sometimes the icon lags and snaps back to its previous place 4. Sometimes letters collide with each other and are a wrong size EXPECTED RESULT 1. The name should fit in the highlighted frame 2. If the cursor is over the shortcut, it must open after a double click regardless 3. The icon should remain in place 4. Letters should adhere to the specified font SOFTWARE/OS VERSIONS KDE Plasma Version: 6.1.2 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION Resolution: 2560x1600 (16:10) Scale: 120% Refresh rate: 120 Hz Font: Noto Sans 13pt
Forgot to mention, my graphics platform is wayland
Can you share your folderview settings: Right click -> Desktop and wallpaper -> Icons
(In reply to David Edmundson from comment #2) > Can you share your folderview settings: > > Right click -> Desktop and wallpaper -> Icons Arrangement: Top to Bottom, Align left Lock in place: No Sorting: Manual Icon size: 4 Label width: Medium Text lines: 2 When hovering over icons: Show folder preview popups Rename: yes Previews: yes Configure Preview Plugins: all apart from text files
Can confirm, it's this bit: > Font: Noto Sans 13pt The height is gridUnit-based, not based on the actual height of the font. And we made gridUnit no longer auto-adjust with the font height.
So, fundamentally we have two options: 1. Stop basing the height on GridUnit here in this code, and explicitly use the metrics of the actual text. 2. Revert the change to make GridUnit static (see Bug 493687) See also Bug 493687 comment 1
*** Bug 496857 has been marked as a duplicate of this bug. ***