After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 105649 - workspace switcher should react on button release, not button press
workspace switcher should react on button release, not button press
Status: RESOLVED DUPLICATE of bug 86590
Product: metacity
Classification: Other
Component: general
unspecified
Other Linux
: Normal minor
: ---
Assigned To: Metacity maintainers list
Metacity maintainers list
Depends on:
Blocks:
 
 
Reported: 2003-02-09 16:14 UTC by Janne
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Janne 2003-02-09 16:14:25 UTC
The workspace switcher works by the user pressing a key combination (suchg
as ctrl+alt+arrow key) to move from one workspace to another.

In rh8, this operation reacts when the user releases all keys. In gnome2.2
(garnome), it reacts on arrow key press. This is suboptimal in my view. The
benefit of not actually switching until the user releases all keys is that
the user can flip along in the small iconic view until the correct
workspace is selected, without having to see (and suffer redrawin of) the
workspaces that are intermediate to the target one. It also means a user
may change their mind and flip back to the original workspace without the
desktop ever changing. Also, with marginal keyboards (keyboards with
contact bounce; cramped laptop keyboards), the immediate switch makes it
more likely that the user overshoots their intended workspace. In all, I
feel a greater sense of control with the kind of delayed execution that the
rh8 setup offered for this operation.
Comment 1 Calum Benson 2003-02-19 15:38:56 UTC
This sounds kind of like a duplicate of #86590...?
Comment 2 Janne 2003-02-19 22:33:02 UTC
Yes, it's a duplicate - sorry. I have added my comments to it instead.
Comment 3 Janne 2003-02-19 22:34:20 UTC

*** This bug has been marked as a duplicate of 86590 ***