Summary: | window grouping doesn't work | ||
---|---|---|---|
Product: | [Unmaintained] plasma4 | Reporter: | michal |
Component: | widget-taskbar | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | andresbajotierra, aseigo, asraniel, eager, nightrow, tampakrap |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Taskbar that should benefit from window groupping |
Description
michal
2009-06-10 15:23:17 UTC
what are the tasks widget settings? Appearance Show tooltips Maximum rows: 2 Grouping & Sorting Grouping by program name (only when taskbar is full) Sorting: alphabetically Unchecking "only when taskbar is full" helps but, belive me, it is full. Actually unchecking "only when taskbar is full" doesn't help much - see attached screenshot. Note that Okular, OpenOffice Writer and Icedove windows are grouped, but KWrite windows are not. Created attachment 34780 [details]
Taskbar that should benefit from window groupping
- Has the situation improved on KDE4.3 ? Thanks I'm not sure. Maybe it's bit better, but still far from perfect. For example right now KWrite instances are being grouped, but OpenOffice windows are not. I'm on kde SC4.4 beta 1, and the situation seems no better. I asked to group windows, without ticking "when taskbar full", and none of the 16 firefox windows i hopened did group. I noticed that each new instance has a new name ("firefox", "firefox <2>" and so), maybe it's the source of the problem ? *** Bug 190290 has been marked as a duplicate of this bug. *** (In reply to comment #7) > I noticed that each new instance has a new name ("firefox", "firefox <2>" and > so), maybe it's the source of the problem ? I don't think so, this is how new instances are named either way. For the record, I couldn't reproduce with latest trunk, could someone please try with 4.4 RC? *** This bug has been marked as a duplicate of bug 201761 *** |