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 760610 - Scrollwheel usage on property editor: Disable scrolling through values of certain types of controls
Scrollwheel usage on property editor: Disable scrolling through values of cer...
Status: RESOLVED FIXED
Product: glade
Classification: Applications
Component: user interface
3.19.x
Other Windows
: Normal minor
: ---
Assigned To: Glade 3 Maintainers
Glade 3 Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-01-14 06:34 UTC by Rod Pullmann
Modified: 2017-11-21 17:57 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Rod Pullmann 2016-01-14 06:34:27 UTC
I use Glade extensively for a wide assortment of designs.  For the most part it is an excellent tool.  However, there is one behavior that drives me nuts.

Imagine scrolling through the Widget Properties pane using the mouse scrollwheel.
Wherever the mouse happens to be positioned in the pane at the start of scrolling is somewhat arbitrary, and the cursor doesn't move much during scrolling.  However, when the pane has scrolled to one or another end of its vertical travel, and the mouse cursor then happens to be positioned over a control like a ComboBox or SpinnerButton, the mouse scrollwheel scrolls through the values of that control instead of scrolling the pane!

A typical example of this is Opacity, which is specified for many widgets, and uses a SpinnerButton; I'm continually discovering this property to be set to some non-default value or another.  The designer has to be quite vigilant and doublecheck that none of his/her scrolling actions have caused properties to have become inadvertently changed.

That actually bit me in a bad way recently, when it was the Resize Mode combobox that was the victim of this behavior.  It became errantly set to Immediate mode, which triggered a GObject bug when this mode is used with certain containers, causing my whole application to crash.  It took hours of experimentation and isolation to discover the root cause, all because of this damnable scrolling behavior.

Since there is no way to distinguish between the various intents for the mouse scrollwheel, I would suggest disabling scrolling through values of these types of controls entirely via the mouse scrollwheel in the Widget Properties pane, or any pane that has such controls, for that matter.
Comment 1 Tristan Van Berkom 2016-01-14 08:16:39 UTC
Yes, this is very annoying indeed.

Your suggestion is good, we should be able to just disable scroll event handling on the property editing widgets inside the property editor. This will of course make it so that you can't scroll through text views for multiline text properties, but the (current) alternative is much worse.
Comment 2 Tristan Van Berkom 2016-01-28 13:33:18 UTC
Fixed in Glade master.

This is not windows specific, updated bug title.

Closing with commit:

commit 094997593cdc006d6f2ba0d5179f223518e56264
Author: Tristan Van Berkom <tristan@upstairslabs.com>
Date:   Thu Jan 28 14:30:42 2016 +0100

    Bug 760610: Disable scroll events on property editor widgets
    
    As described in the bug, this is only harmful and annoying that
    combo boxes handle scroll events, of course, the whole purpose
    of combo boxes is to place them inside scrolled windows ;-)
Comment 3 Jeroen Bollen 2017-11-21 17:57:29 UTC
Has this fix shipped yet? It still behaves as described in the OP for me.