Bug 244719 - Pointer goes to top left when dragging a new maximised window
Summary: Pointer goes to top left when dragging a new maximised window
Status: RESOLVED DUPLICATE of bug 228815
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-15 12:39 UTC by Bruno J.
Modified: 2011-02-23 16:56 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bruno J. 2010-07-15 12:39:04 UTC
Version:           unspecified (using Devel) 
OS:                Linux

The window has to be created already maximised for the bug to happen.

Reproducible: Always

Steps to Reproduce:
To reproduce it I use amarok.

1- Set amarok window to maximised
2- Click the systray icon to hide it
3- Click again to make it appear back ( so that the window has been created already maximised)
4- Drag it to un-maximise it (click the title bar or any inactive part of the window (KDE 4.5))


Actual Results:  
Wherever you clicked to drag the window while maximised the mouse pointer goes to top left.

Expected Results:  
The pointer should stay where it has been clicked on the window.
Should work like it does when un-maximising a window that has not been created in a maximised state.

KDE 4.5 RC2
Comment 1 Bruno J. 2010-10-05 18:25:44 UTC
Issue still present in 4.5.1
Comment 2 Thomas Lübking 2010-10-05 18:36:34 UTC
does it happen with any (widget) style or just oxygen/bespin?
Comment 3 Bruno J. 2010-10-05 23:16:40 UTC
Using another widget and window decoration than oxygen I can reproduce it. 
Can you not reproduce it ?
Comment 4 Thomas Lübking 2010-10-06 00:22:24 UTC
i know that those styles warp forth & back the pointer after "easy dragging" since the client otherwise get's confused about mouse events.
however, after trying (i usually avoid max'd windows :-) i can reproduce this, but in a different way:
the clients top left corner is moved to the pointer, while the pointer remains in its position. -> is this what you observe?
Comment 5 Hugo Pereira Da Costa 2010-10-06 00:55:15 UTC
Thomas: note that the original report also mentions that it happens when dragging from the titlebar, "(click the title bar or any inactive part of the
window (KDE 4.5))", for which I don't think there is any playing around with the mouse position. Is this also your observation ? 

If no, that might just be a different bug ...

If yes, then I don't think this is related to the way bespin/oxygen (or Qtcurve, for that matter) perform window dragging. 

I can't reproduce the bug because I don't have the snapping thingy enabled. 
(so you basically cannot move/un-snap maximized windows). 
Maybe its a 'snap' related bug ...
Comment 6 Hugo Pereira Da Costa 2010-10-06 00:57:02 UTC
PS: in fact, if I enable the "Maximize window by dragging ..." I can reproduce the behavior mentionned by Thomas. This from both the titlebar and the content. 
I do think its a 'snap' 'feature'.
Comment 7 Bruno J. 2010-10-06 18:33:42 UTC
(In reply to comment #4)
> i know that those styles warp forth & back the pointer after "easy dragging"
> since the client otherwise get's confused about mouse events.
> however, after trying (i usually avoid max'd windows :-) i can reproduce this,
> but in a different way:
> the clients top left corner is moved to the pointer, while the pointer remains
> in its position. -> is this what you observe?

Yes that is what I observe, the pointer stays in its position and the window is moved so that the top left corner gets under the mouse.
For example if after the maximized window I click on the max right I can before the close buttons and drag it the windows is almost not visible as it is out of the screen due to the move.
Comment 8 Bruno J. 2011-01-06 18:06:37 UTC
Issue still present in KDE SC 4.6 RC2
Comment 9 Thomas Lübking 2011-02-23 16:56:58 UTC
this is basically a dupe of 228815 kinda "bad original geometry condition"

*** This bug has been marked as a duplicate of bug 228815 ***