Currently, the Cycle and minimize action when wheeling the mouse is like below: 1, Mouse up: switch between tasks and unminimize them 2, Mouse down: only minimize tasks. If all tasks are minimized, do nothing (*) What do you think if after (*), if the user continues to wheel the mouse down, we show then hide the next task one by one? This will return only one window on the screen which is very clean.
Btw, currently, when you wheel down, if a window is maximized, it will be unmaximized first, then it will be minimized. Is that needed? Can we remove the Unmaximized action?
(In reply to trmdi from comment #1) > Btw, currently, when you wheel down, if a window is maximized, it will be > unmaximized first, then it will be minimized. Is that needed? Can we remove > the Unmaximized action? Because we can also toggle the maximized state with the Double click action very quickly. So that is not needed.
Today I try these Cycle... actions again, and I found that, actually, the behaviors of Cycle and Minimize are a bit confusing. 1, Look at the behavior of Cycle through Tasks: - the behavior when Wheel down and Wheel up are the same, just change from left->right to left<-right. 2, But for Cycle and Minimize: - the behavior when Wheel down and Wheel up are different, see #1 for more details. Its name is "Cycle and minimize" but why it unminimize all windows when wheel up the mouse? So I suggest to make the behavior of (2) when Wheel down and up the same. It means, when use "Cycle and Minimize": - Wheel up: minimize all, activate the next task. - Wheel down: minimize all, activate the previous task. (when the task is the first or the last one, continue instead of do nothing (*))
Ah, sorry, I misunderstood it. :(