Bug 217393

Summary:	minimizing a grouped window via tray icon loses grouping
Product:	[Plasma] kwin	Reporter:	Milian Wolff <mail>
Component:	general	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED NOT A BUG
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Unspecified
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Milian Wolff 2009-12-05 01:17:40 UTC

Version:            (using Devel)
Installed from:    Compiled sources

To reproduce:

- group e.g. Kmail or any other app with a tray icon that lets you minimize/maximize it with any other window
- minimize said app via it's tray icon
- maximize it again via it's tray icon

Expected behavior:

- app is again in the same group as before

Actual behavior:

- app is ungrouped

Also note that, when minimizing an app via context menu in the task manager results in minimizing the whole group. Could be OK as well, dunno. Actually I think this is a tough one to solve "correct" for everyone. I'd even somehow (grudgingly ;-) ) accept a WONTFIX since this could be very complicated.

Comment 1 Thomas Lübking 2009-12-05 01:56:00 UTC

Assuming you're referring to tabbing:
"Minimizing" to systray is in fact (usually) closing the window (and "unminimizing" creates another one), so I fear this is the "Won't fix" part of your report :-(

As for the other one:
a stacked behind window /should/ be unmapped anyway (i /assume/ kwins implementation does that), so if you click a not visible tabbed window in the taskbar, it should be brought to front (unminimized) and if you click the window for an active tab, it should be minimized.

As all other windows in that tab /are/ allready minimized, it would not be replaced by one.

The two ways out of this should be to keep inactive tabbed windows mapped (ewww...) or add an intermediate state (mapped, groupmapped, unmapped) to the *WM_STATE atom of the ICCCM or NETWM spec (or rather a kde propriatary atom...)
:-\

Comment 2 Milian Wolff 2009-12-05 02:18:58 UTC

Sorry, turns out this is a KMail misbehavior after all. Works fine with e.g. Quassel. See Bug 217397.