GNOME Bugzilla – Bug 325261
Mousewheel not functioning properly with multiple rows.
Last modified: 2005-12-31 09:15:56 UTC
Please describe the problem: When the workspace switcher is set to display muliple rows, using the mousewheel will select the wrong desktop. ex: IT displayes the desktops numbered like this 1 2 3 4 Scrolling the mousewheel down from 1 will go to dektop 3 instead of 2. This problem persists if the workspace switcher is set to show only one workspace at a time, based on how many rows are chosen(the box is inactive, yet it effects the action). Steps to reproduce: 1. Set the workspace switcher to use 2 or more rows. 2. scroll the mousewheel over the workspace switcher. 3. Change the workspace switcher to display only one desktop at a time, while leaving the number of rows at 2 or higher. 4. see #2 Actual results: Order 1>3>2>4 Expected results: Order 1>2>3>4 Does this happen every time? Yes Other information:
See bug #320751. *** This bug has been marked as a duplicate of 320751 ***
It's not quite the same problem as the other one. I understand why it works the way it does when showing multiple rows, but when choosing to only show the active workspace instead of showing it in rows and columns the scrolling order is still affected based on how many rows are set to be displayed, but the box to change that info is inactive, so it should not have an effect.
Well, the fact that it only shows the current workspace doesn't change the workspace layout: for example, when you switch workspace with Ctrl+Alt+Left/Right, you see the layout. The fact that the box to change the number of rows is inactive can be considered a bug in the dialog. See bug 80536 about the confusion created by "show only the current workspace". I understand the problem, though. Maybe what should be changed is the way workspace are named by default, or the way we move them when adding some rows. But I think the scrollwheel as it is right now is more consistent with what the user feels. If you have a good proposition on how to fix this, please reopen the bug or file a new bug. Thanks,