[kwin] [Bug 405450] Extend Maximize/Restore action into a tri-state Maximize/Restore/Minimize action

2021-10-17 Thread danspark
https://bugs.kde.org/show_bug.cgi?id=405450

danspark  changed:

   What|Removed |Added

 CC||sxh...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 405450] Extend Maximize/Restore action into a tri-state Maximize/Restore/Minimize action

2019-03-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=405450

--- Comment #5 from pmarget...@gmail.com ---
(In reply to Christoph Feck from comment #4)
> Unless you want to step up and implement and maintain the added code for new
> features, there is little point in piling up more feature requests in
> bugzilla. That might come as a surprise, but considering the experiences
> made in the last years, there is no other option.

There is little point in implementing the code if this bug is instantly marked
as RESOLVED INTENTIONAL.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 405450] Extend Maximize/Restore action into a tri-state Maximize/Restore/Minimize action

2019-03-13 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=405450

--- Comment #4 from Christoph Feck  ---
Truth is, Kwin developers are already swamped with bug reports (either valid,
or invalid, because they are vendor driver specific). Adding more options to
KWin will only increase maintainance burden.

Unless you want to step up and implement and maintain the added code for new
features, there is little point in piling up more feature requests in bugzilla.
That might come as a surprise, but considering the experiences made in the last
years, there is no other option.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 405450] Extend Maximize/Restore action into a tri-state Maximize/Restore/Minimize action

2019-03-13 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=405450

--- Comment #3 from pmarget...@gmail.com ---
...cont.
Furthermore, you allow Double click: minimize action (which can't be undone in
the same way), Minimize is also in the list for Left, Middle and Right buttons,
and you can even have it activate on Window Actions->Inner Window,Titlebar &
Frame in combination with a modifier key. So why is wheel action an exception
all of a sudden?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 405450] Extend Maximize/Restore action into a tri-state Maximize/Restore/Minimize action

2019-03-13 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=405450

--- Comment #2 from pmarget...@gmail.com ---
(In reply to Martin Flöser from comment #1)
>It makes zero sense to also include minimize in it. 
If a window isn't maxized, it would make sense that mouse wheel down minimizes
it. What's your argument for why exactly it makes zero sense?

>Even more minimize in that list would be unacceptable as it's an action
> which cannot be reversed in the same way.
Is this a KDE design principle written somewhere? There are other ways to
restore a minimized window: alt-tabbing, task manager...

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 405450] Extend Maximize/Restore action into a tri-state Maximize/Restore/Minimize action

2019-03-13 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=405450

Martin Flöser  changed:

   What|Removed |Added

 Resolution|--- |INTENTIONAL
 Status|REPORTED|RESOLVED

--- Comment #1 from Martin Flöser  ---
Maximize/Restore are the options to go from maximize to restore and from
restore back to maximize. It makes zero sense to also include minimize in it.
Even more minimize in that list would be unacceptable as it's an action which
cannot be reversed in the same way.

-- 
You are receiving this mail because:
You are watching all bug changes.