Bug 86847 - 3.3 rc1: "Allow moving and resizing of maximized windows" option has no effect
Summary: 3.3 rc1: "Allow moving and resizing of maximized windows" option has no effect
Status: RESOLVED FIXED
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
: 87449 89291 90369 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-08-09 14:44 UTC by jakubpol
Modified: 2004-09-29 15:40 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jakubpol 2004-08-09 14:44:49 UTC
Version:            (using KDE KDE 3.3.0)
Installed from:    Gentoo Packages
Compiler:          gcc-3.4.1-r2 
OS:                Linux

I have installed KDE 3.3 rc1 and found that I can always move and unmaximize maximized windows, irregardless of whether the option "Allow moving and resizing of maximized windows" is checked or not (it used to work before).

I have asked other people on a forum, and got one reply that it works, so if it works for you, please close the bug report.

Regards,

Jakub
Comment 1 miro 2004-08-10 10:45:39 UTC
With kde3.3rc2 (3.2.92). With no previous .kde directory, when un-checking "Allow moving and resizing..." the maximize button disappears. Double click maximizes but I can't restore the window afterwards (even the "restore" menu item is disabled)

Used style & window decoration: plastik.

Regards,
Miro
Comment 2 Lubos Lunak 2004-08-10 11:18:05 UTC
You should of course always be able to unmaximize maximized windows, regardless of the option.
The fact that you can actually move and resize the windows even with the option turned off is a consequence of the option being misnamed. The original intention of it was something like "hide borders for maximized windows" (so that people can move the mouse to the leftmost or rightmost position and be still inside the window). I changed the meaning of the option recently due to some technical reasons, but I couldn't change the text due to text freeze.
Do you consider that as a problem?
Comment 3 jakubpol 2004-08-10 12:35:18 UTC
I certainly do not consider that a problem, I just thought it was a bug that managed to slip through (although I do find the name of the option a bit misleading). Thank you very much for your explanation.

Regards,
Jakub
Comment 4 jakubpol 2004-08-10 12:36:40 UTC
There is no bug I just misunderstood the option so marking as resolved.
Comment 5 Luciano Montanaro 2004-08-11 16:16:50 UTC
Lubos, do we really need this option at all?
I think the option was originally there because there was a trade-off the user
had to do, depending on the preferred functionality:
one could have either small borders for maximized windows, or movable maximized
windows, but not both. Since the limitation is no longer in effect, is this
additional tweak really necessary, or should it be to the decoration to offer
the option? 
I'd go for the latter, also because with current wording, users will be quite a bit confused.
Comment 6 Ranma 2004-08-12 07:16:36 UTC
I don't get it, this means that I can move maximized windows now and there is no way to change this behaviour?, I see this a little illogical, since if I move a maximized window, it won't see the whole window anymore, if I want to move a window I do it with one that doesn't fill my screen.
Maybe it's just me, but I don't like it. I liked the old way where you could choose, as so many things in KDE and one of the reasons I love it.
Comment 7 Lubos Lunak 2004-08-12 12:41:08 UTC
Ranma: What exactly is your problem? If you don't want to move maximized windows, then simply do not move them?
Comment 8 Ranma 2004-08-18 19:53:32 UTC
Mi problem is that I want the window to stay in the same place no matter what, sometimes I accidentally click and move the mouse and my window moves. Or I use an application where I use the mouse combined with shift, ctrl and alt. sometimes I make a mistake and press the ¨meta¨ key and actidentally move the whole window.
Is just that I don´t see the point of disabling this, it was nice as an option, so we can choose. There are other people that think the same, I´ve seen other bug reports with the same problem.
Comment 9 Jason W 2004-08-20 10:44:16 UTC
as ranma said, sometimes a maximized window is moved accidentally.  Since it is then no longer "maximized" it can no longer be restored to it's previous unmaximized size.  

Example: maximize a 700*500 window.  One expects to be able to restore it to 700*500, but if one accidentally moves it while maximized, it can no longer be restored to 700*500.

I expect a maximized window to be static.  There have been multiple bug reports about this option no longer working and it has been mentioned elsewhere.

I understand what the option was originally meant for but that really doesn't work as well as it should.. it is still impossible to move the mouse to the edge of the screen and use a scrollbar in a maximized window.  I much preferred the effect of making the window unmoveable: please reconsider removing that option.
Comment 10 Christoph Wiesen 2004-08-26 02:17:16 UTC
Personally I'd say the option to make maximized windows non-moveable (yes it happens to me too by accident) so that one can always restore the window to the previous size. Maybe it's not such a big thing at all, but the text for this option is wrong at the moment which might be an issue for some.

But no matter what, please don't (ever) remove the possibility to disable windo borders on maximized windows. The ability to click blindly on the topmost right corner of the screen to close a window or doubleclick on any pixel at the center top of the screen to restore a window is just too valuable - IMO overall usability would suffer if windows always showed borders.
Comment 11 Lubos Lunak 2004-08-26 12:35:45 UTC
*** Bug 87449 has been marked as a duplicate of this bug. ***
Comment 12 Lubos Lunak 2004-08-26 12:37:02 UTC
Ok.
Comment 13 Lubos Lunak 2004-08-26 12:37:33 UTC
*** Bug has been marked as fixed ***.
Comment 14 Lubos Lunak 2004-09-13 13:21:43 UTC
*** Bug 89291 has been marked as a duplicate of this bug. ***
Comment 15 Lubos Lunak 2004-09-29 15:40:18 UTC
*** Bug 90369 has been marked as a duplicate of this bug. ***