Bug 302778 - launchers too tiny and space between them too big
Summary: launchers too tiny and space between them too big
Status: RESOLVED DUPLICATE of bug 321128
Alias: None
Product: plasma4
Classification: Plasma
Component: widget-taskbar (show other bugs)
Version: 4.8.2
Platform: Mageia RPMs Linux
: NOR minor
Target Milestone: ---
Assignee: Plasma Bugs List
: 303725 (view as bug list)
Depends on:
Blocks: extramile
  Show dependency treegraph
Reported: 2012-06-30 07:04 UTC by Denis Prost
Modified: 2013-06-15 15:09 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

panel screenshot (31.29 KB, image/png)
2012-06-30 07:06 UTC, Denis Prost

Note You need to log in before you can comment on or make changes to this bug.
Description Denis Prost 2012-06-30 07:04:00 UTC
when one selects, by right clicking on a started application button, to have it displayed as launcher when it is not started, the launcher that appears after it is closed is too small : it would be visually more comfortable if it were the same size as the classical panel launchers. Also, the space between two launchers is too big, losing space in panel. Maybe this is a matter of taste. If it is, it would be nice to have an option to set space and icon sizes in taskbar config dialog.
(see attached screenshot : launchers for zim and systemsettings) 

Reproducible: Always
Comment 1 Denis Prost 2012-06-30 07:06:38 UTC
Created attachment 72230 [details]
panel screenshot

shows the problem described above for systemsettings and zim launchers
Comment 2 Myriam Schweingruber 2012-08-06 01:49:53 UTC
Added to The Extra Mile
Comment 3 Will Stephenson 2012-09-21 20:48:06 UTC
*** Bug 303725 has been marked as a duplicate of this bug. ***
Comment 4 Gernot Wieprecht 2013-01-31 11:55:51 UTC
In my humble user's mind those "extra launchers" should have exactely the same size and space between them as the other launchers in the panel, their size too should be controlled by the panel icons size settings in systemsettings.
Comment 5 Pascal d'Hermilly 2013-01-31 13:38:59 UTC
I can confirm this for KDE 4.10 RC3
Comment 6 Aaron J. Seigo 2013-06-15 15:09:54 UTC
The problem has changed slightly in current master which will be for 4.11

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