(In reply to Thomas Pfeiffer from comment #13) > (In reply to Martin Gräßlin from comment #11) > > I'd say two groups of behavior: > > * might change during life time of window (e.g. maximize) > > * might not change during life time of window (e.g. quick help)
> If, however, the windeco _can_ know whether the button is temporarily or > permanently unavailable, then of course temporarily unavailable buttons > should be disabled and permanently unavailable ones should be hidden. *cough* "might" *cough* Actually every button *might* be temporarily unavailable - it's more a matter of likelihood. But *usually* a feature will be available or not for a window as long as it exists - and it's not predictable whether the eg. the client will later on release the size constraints. @Martin I'm actually not sure about esp. the context help here - a client could pot. provide it depending on which kcm is currently loaded or which tab is the current in a QTabWidget - I didn't find a comment on whether WM_PROTOCOLS must not be updated after mapping. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1175299 Title: kwin Plastik decoration displays the help-button wrong To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1175299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs