| Summary: | Add a new behavior to "Cycle and minimize" | ||
|---|---|---|---|
| Product: | [Unmaintained] lattedock | Reporter: | trmdi |
| Component: | application | Assignee: | Michail Vourlakos <mvourlakos> |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | wishlist | ||
| Priority: | NOR | ||
| Version First Reported In: | git (master) | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
trmdi
2021-01-10 14:48:17 UTC
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. :( |