Bug 361780

Summary:	Plasma desktop shortcuts taking up twice the space
Product:	[Plasma] plasma4	Reporter:	Bit Twister <bittwister2>
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Mageia RPMs
OS:	Linux
URL:	https://bugs.mageia.org/attachment.cgi?id=7453
Latest Commit:		Version Fixed In:

Description Bit Twister 2016-04-14 21:25:36 UTC

Plasma desktop shortcuts taking up twice the space as mga5, even though icon size is smaller on mga6.

Qt: 4.8.7
KDE Development Platform: 4.14.18
kde4-config: 1.0


Reproducible: Always

Steps to Reproduce:
Desktop: Plasma Layout: Folder Theme: Oxygen    Window Decorations: plastik
Desktop effects are disabled.

1. systemsettings5->Appearance Workspace Theme->Look And Feel
   select Oxygen

2. systemsettings5->Appearance->Icons  select Advanced tab, set Size: 16

3. systemsettings5->Window Behavior click Moving tab, set no border/window/center  snap zone and uncheck Snap windows only when overlapping

4. Right click blank spot on desktop, Select Folder Settings->Icons
   move Size: slider all the way to the Left

5. Right click blank spot on desktop, select Create New Link->New Link to app
   name it xterm1, repeat for xterm2, xterm3, xterm4

6. now arrange them in two rows, xterm 1 and 2, second row with xterm 3 and 4
   as close as possible to each other.



Actual Results:  
mga6 icon size 16

Expected Results:  
mga5 icond size 22

Comment 1 Nate Graham 2018-06-08 18:28:20 UTC

Hello!

This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug has already been resolved in Plasma 5.

Accordingly, we hope you understand why we must close this bug report. If the issue described  here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting

If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging

Thanks for your understanding!

Nate Graham