Oxygen's new window-move feature fatal for KJumpingCube game

[Martin Gräßlin]

On Friday 18 June 2010 08:50:35 Ian Wadham wrote:
> Why is the feature necessary
> and is its benefit worth the possible disruption to existing applications
> and the extra work for their maintainers and end users?
This feature is important to increase the consistency of window management. 
Our default window decoration blends with the default widget style. Joe User 
cannot understand why it is possible to move the window on one spot and one 
pixel below it isn't possible any more.

If we don't introduce such features in the style we face issues like 
applications adding support for it (e.g. Chromium) which is much worse at it 
introduces inconsistency between all open windows and it is likely that each 
app has a different implementation which can cause problems when for example 
drag delay is not implemented properly (see e.g. Chromium). The Oxygen drag 
feature has been implemented with feedback from kwin hackers to ensure that 
the behavior is reliable and that there are no differences between dragging 
the titlebar and the chrome.

I also think that this feature in Oxygen helps all of us to identify bugs in 
the applications. As the introduction of the feature shows a widget style can 
do such things (and it has been done before, e.g. Bespin) and the app cannot 
rely on Oxygen being the only widget style. If a user would use Bespin the 
same bug might have appeared and it would not have been so easy to spot the 
source of the bug. There is also the chance that distributions change such 
behavior, e.g. Ubuntu introduced a click-to-drag in Lucid's GTK style. I don't 
know how Qt apps behave in respect to this feature in Ubuntu Lucid, but I 
could imagine that your app is showing the same problem there.

Regards
Martin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 316 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20100619/187f4f75/attachment.sig>