Re: [Fwd: scroll wheel mouse configuration]
- From: Skunk Worx <skunkworx verizon net>
- To: gnome-list gnome org
- Subject: Re: [Fwd: scroll wheel mouse configuration]
- Date: Sun, 14 Jan 2007 17:06:53 -0800
On my mac mini, which uses the same mouse via kvm, the scroll wheel only
seems to affect sliders (pane, volume) but I have yet to see a combo box
change using only the scroll wheel. This feels right to me.
---
John
Skunk Worx wrote:
That's exactly what I'm hoping for--a way to change the default
behavior, not necessarily force my wishes on anyone else.
I don't have too much of a problem with auto switching into unfocused
main windows and then scrolling. It seems a little strange, but no big deal.
My real concern is what I saw last week...an application my company
wrote has a scrollable panel with sparsely placed combo boxes, etc. They
are in a table.
As the user scrolled the pane with the mouse wheel, the pointer happened
to enter a combo box. It stayed there (stopped scrolling the panel) then
began scrolling the combo contents and selecting new values.
The new values in this case were bitmasks sent to a chipset on our
plugin board. The board stopped working until reset.
At no time did the user click either button or the wheel...only scrolled
the wheel. By scrolling the mouse wheel, focus went into the child
widget (a combo box in this case) and a value change occurred with no click.
Windows and OS X don't do this, not by default anyway. I suppose we can
start digging into the masks in our apps if no solution exists elsewhere.
---
John
Jason Brower wrote:
Ironically I like this feature. Nothing gets me more upset than having
to click to get TO a window when I can quickly scroll. It come in very
handy because the windows doesn't come to focus. It simple
moves/scrolls the window. I like it when I am working on something and
have a pdf in evince and my programing on the right. I can set things
so that I don't have to have the on top feature. But can have the pdf
scroll withing having to click on it and bring it in front of
everything. I say we keep it the way it is... or provide an option to
make your "feature" available.
Jason Brower
-------- Forwarded Message --------
From: Skunk Worx <skunkworx verizon net>
To: gnome-list gnome org
Subject: scroll wheel mouse configuration
Date: Sat, 13 Jan 2007 15:04:07 -0800
I am using Fedora Core 6 and gnome and do not like the default behavior
of the pointer when using a scroll wheel mouse.
For example if I have two applications open, and slide the mouse from
one to the other, the focus does not follow. I am okay with that, that
is configurable via a menu setting, stay with me...
However, rotating the scroll mouse over (say) a combo box on the
unfocused window starts changing the values in that combo box. Not just
scrolling through the values, actually scrolling the values and slecting
them! With no mouse click.
As stated, the mouse wheel rotation both scrolls and activates the
change. Open two instances of OpenOffice writer and move the pointer
over the font size combo box. Scrolling the wheel (no click) scrolls the
list and activates the size as it scrolls. This seems very, very wrong.
Now imagine a application with a scrollable pane, sparsely populated
with combo boxes or whatnot. The pointer goes over the pane, the scroll
wheel gets bumped or nudged, and the pane scrolls slightly. Ignoring the
lack of main window focus issue, fine again...
The problem is, scrolling the pane and having the pointer enter a combo
box as the pane slides, now the pointer stops in the combo box and
starts altering the contents of the combo...not just scrolling the
values, but actually performing a selection of the values with no mouse
click at any time. This just seems very, very wrong.
How can I change this or disable the scroll mouse entirely (other than
the obvious of changing out the mouse)?
Is this a gnome or xorg.conf configuration issue? I have asked on the
fedora list and they don't seem to understand what I am talking about.
Neither my Mac mini running tiger nor my windows machines exhibit this
(what I consider) destructive behavior.
Thanks,
John
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]