Bug 390531

Summary: Default icon grid doesn't leave enough horizontal and vertical space for file and folder titles
Product: [Plasma] plasmashell Reporter: Nate Graham <nate>
Component: FolderAssignee: Eike Hein <hein>
Status: RESOLVED DUPLICATE    
Severity: normal CC: kde, plasma-bugs, simonandric5
Priority: NOR    
Version: master   
Target Milestone: 1.0   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: Spacing, title width, and max number of lines in Folder view and Dolphin

Description Nate Graham 2018-02-15 23:59:32 UTC
Created attachment 110696 [details]
Spacing, title width, and max number of lines in Folder view and Dolphin

Files and Folders in Folder View always look really cramped because long titles very easily get split up into multiple lines and then elided. The behavior here is a bit too aggressive, I think. I see a lot of user complaints about it.

Part of the problem is the default maximum number of lines (2), but another part is that the width available for titles is so narrow that long-ish words often get chopped up into multiple lines right in the middle. For the same sized icons, Dolphin's icon view offers more horizontal space and slightly larger padding between icons. See attached screenshot from my own machine.
Comment 1 Eike Hein 2018-02-16 00:16:53 UTC
I can look into the titles maybe, but the padding won't change - it was actually reduced twice, because of great repeated user clamoring both times, and people are much happier now with the tighter grid.
Comment 2 Nate Graham 2018-02-16 00:20:33 UTC
I can understand that. We had the same problem at Apple for more than a decade; people always complained that the padding was too high. Eventually we solved it with a slider you can use to change the padding between icons, which makes sense to me because this is the kind of thing where you're never going to please everybody with an immutable setting.
Comment 3 Kai Uwe Broulik 2018-02-16 10:17:21 UTC
Please no slider..
Comment 4 Nate Graham 2018-03-02 23:07:12 UTC

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