Bug 452140 - Spacing between Icons too large in kfilewidget
Summary: Spacing between Icons too large in kfilewidget
Status: CLOSED NOT A BUG
Alias: None
Product: frameworks-kio
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KIO Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-04-01 06:56 UTC by Evert Vorster
Modified: 2022-04-01 19:40 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Evert Vorster 2022-04-01 06:56:07 UTC
SUMMARY
***
Spacing between Icons too large in kfilewidget in icon view
***


STEPS TO REPRODUCE
1. Use an application that incorporates kfilewidget.
2. Switch the file browser to Icon View
3. Cry about the huge waste of screen space... :P

OBSERVED RESULT
The spacing between Icons in the icon view is almost as large as the icons themselves. 

EXPECTED RESULT
Screen space to be used for displaying images, not blank space.

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: Arch Linux, fully up to date.

ADDITIONAL INFORMATION
This may be related to #452139 and maximum Icon size. I am using this on a 4K monitor with no scaling applied. 
When doing graphical work, the desire is to maximize the screen area for actual images, and only a few pixels are necessary to distinguish one icon from the next. 
The whole point of using icons is to display pictures, and it stands to reason to have those icons use up the maximum amount of screen space that they can. 

Currently it looks like the columns of icons are spaced to allow for the text below the icons. When changing the scale of the icons, there should be a size where the icons almost touch their neighbor, and be a little wider than the text below.
Comment 1 Nate Graham 2022-04-01 19:40:47 UTC
> This may be related to #452139 and maximum Icon size. I am using this on a 4K monitor with no scaling applied. 
Same answer as Bug 452139. :)