Bug 235091

Summary:	screen edge maximize does not return window to original position when dragged across dual screen
Product:	[Plasma] kwin	Reporter:	Myk Taylor <myk002>
Component:	general	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Myk Taylor 2010-04-22 19:35:38 UTC

Version:            (using KDE 4.4.2)
OS:                Linux
Installed from:    Gentoo Packages

I have the following setup:

Dual screen (NVidia Twinview setup)
Panel on bottom of left screen (as per default)
I allow resizing of maximized windows (if that is relevant)

If I have a non-maximized window on the right screen and drag it to the top of the left screen, it maximized correctly in the left screen.

If I then drag the maximized window back to the top of the left screen, the window will flicker back to its original position on the right screen, but then jump to the upper left corner of the left screen.

If I drag the window on the right screen to the top of the right screen, it maximizes correctly on the right screen.  And then if I drag it to the top of the right screen again, it resizes back to its original position on the right screen correctly as well.

Comment 1 Martin Flöser 2010-04-22 19:41:55 UTC

*** Bug 235093 has been marked as a duplicate of this bug. ***

Comment 2 Martin Flöser 2010-04-22 19:44:17 UTC


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

Comment 3 Myk Taylor 2010-04-22 20:51:32 UTC

I do not believe this bug is a duplicate of bug 228815 (which I read before filing this bug)  That bug refers to windows that unexpectedly unmaximize (restore?) when moved from the top of the screen.  This bug is about incorrect positioning of the window when it is intentionally unmaximized in the particular case of a dual-screen setup.  There may be a common cause, in which case the "duplicate" status is ok, but the symptoms seem quite different.

Comment 4 Myk Taylor 2010-04-22 20:55:30 UTC

Hi Martin,

I added this comment to the bug, but I didn't see your email on the list and I wanted to make sure it got to you:

I do not believe this bug is a duplicate of bug 228815 (which I read before
filing this bug)  That bug refers to windows that unexpectedly unmaximize
(restore?) when moved from the top of the screen.  This bug is about incorrect
positioning of the window when it is intentionally unmaximized in the
particular case of a dual-screen setup.  There may be a common cause, in which

Thanks,
Myk
case the "duplicate" status is ok, but the symptoms seem quite different.

--- On Thu, 4/22/10, Martin Gräßlin <kde@martin-graesslin.com> wrote:

From: Martin Gräßlin <kde@martin-graesslin.com>
Subject: [Bug 235091] screen edge maximize does not return window to original position when dragged across dual screen
To: myk002@yahoo.com
Date: Thursday, April 22, 2010, 10:44 AM

https://bugs.kde.org/show_bug.cgi?id=235091


Martin Gräßlin <kde@martin-graesslin.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |DUPLICATE




--- Comment #2 from Martin Gräßlin <kde martin-graesslin com>  2010-04-22 19:44:17 ---


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

Comment 5 Martin Flöser 2010-04-22 21:04:19 UTC

yes I am pretty sure it is the same issue as I investigated the one in bug 228815. The window "jumps back" to the position where it was before it was maximized. The same thing happens here, so from a development point of view it is a duplicate, because fixing the one will fix the other.

Comment 6 Myk Taylor 2010-04-22 21:14:18 UTC

(In reply to comment #5)
> yes I am pretty sure it is the same issue as I investigated the one in bug
> 228815. The window "jumps back" to the position where it was before it was
> maximized. The same thing happens here, so from a development point of view it
> is a duplicate, because fixing the one will fix the other.
I'm just making sure here that this is indeed a duplicate: There is a distinct difference here.  The window jumps to a position that it never occupied before, and it only happens in a dual screen setup.  I am using 4.4.2, and I could not reproduce the bug described in bug 228815, which was reported for 4.4.0.