Bug 312031 - Task launcher icon uses too much space on a two-row task manager
Summary: Task launcher icon uses too much space on a two-row task manager
Status: RESOLVED FIXED
Alias: None
Product: plasma4
Classification: Unmaintained
Component: widget-taskbar (other bugs)
Version First Reported In: 4.9.2
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-21 11:00 UTC by tosiara
Modified: 2013-06-05 23:19 UTC (History)
2 users (show)

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


Attachments
Single row task manager (9.94 KB, image/png)
2012-12-21 11:01 UTC, tosiara
Details
Multi row task manager (12.09 KB, image/png)
2012-12-21 11:01 UTC, tosiara
Details

Note You need to log in before you can comment on or make changes to this bug.
Description tosiara 2012-12-21 11:00:20 UTC
When task manager panel has one row the task launcher looks pretty ok: http://img-fotki.yandex.ru/get/5641/73339514.25/0_7c6f7_271cd03c_orig

But when panel is full and switches to two-row display, launcher placeholder uses too much space like being not a button, but task: http://img-fotki.yandex.ru/get/6442/73339514.25/0_7c6f8_6fdbdcae_orig

Reproducible: Always

Steps to Reproduce:
1. Pin Dolphin to task manager (create task launcher)
2. Open some windows until task manager adds new row
3. See task launcher occupies too much space for button
Actual Results:  
Task launcher button uses space same as running task

Expected Results:  
Task launcher should remain as a button and use less space
Comment 1 tosiara 2012-12-21 11:01:09 UTC
Created attachment 75957 [details]
Single row task manager
Comment 2 tosiara 2012-12-21 11:01:33 UTC
Created attachment 75958 [details]
Multi row task manager
Comment 3 Frank Steinmetzger 2013-02-08 16:12:12 UTC
This is a duplicate of #278910, which in turn seems to be a dupe of #264080.
Comment 4 David Edmundson 2013-06-05 23:19:45 UTC
Thank you for your report.

The taskbar applet has been completely rewritten for KDE Workspaces 4.11
I cannot reproduce this bug with the new version.

Please reopen this bug if you encounter this in 4.11 onwards.