Bug 109741 - Extend taskbar buttons to use all available space
Summary: Extend taskbar buttons to use all available space
Status: RESOLVED FIXED
Alias: None
Product: kicker
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR wishlist
Target Milestone: ---
Assignee: Aaron J. Seigo
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-28 03:00 UTC by Vlad C.
Modified: 2005-10-26 16:31 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
Taskbar button prematurely cut off (23.89 KB, image/png)
2005-07-28 03:02 UTC, Vlad C.
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Vlad C. 2005-07-28 03:00:39 UTC
Version:            (using KDE Devel)
Installed from:    Compiled sources
OS:                Linux

Taskbar buttons are often cut even though there is plenty of space available to their right. This needlessly prevents long window titles from being displayed completely.

Please see screenshot below. 
Thanks!
Comment 1 Vlad C. 2005-07-28 03:02:34 UTC
Created attachment 11960 [details]
Taskbar button prematurely cut off

Screenshot (taken from JLP's Blog) that shows how a taskbar button titled “K
Desktop Environment – Conque” is prematurely cut off even though there is
space for it to be extended to the right.
Comment 2 Nick Matteo 2005-10-26 01:29:03 UTC
You can fix this by editing your .kde/share/config/ktaskbarrc and adding or editing the line
MaximumButtonWidth=1000


Taskbar buttons will then expand to fill the whole taskbar until there are more than the first column, at which point they will be subdivided, and so on.  This should be exactly the behaviour you want.

Ideally, you could get behaviour where, as long as there is space available, the column of taskbar buttons is as wide as the longest title in that column(and not wider), but that would be more complex.
Comment 3 Aaron J. Seigo 2005-10-26 16:31:25 UTC
making the columns variable width would also be a bit ugly imo.. in any case, you are correct that this bug is closable with that configuration option.