kcombobox wheelmouse scrolling
Aaron J. Seigo
aseigo at olympusproject.org
Sun Sep 29 18:29:05 BST 2002
-----BEGIN PGP SIGNED MESSAGE-----
On Saturday 28 September 2002 01:05, Stephan Kulow wrote:
> The reason is that it's just too easy to change the combo
> box value without an option to revert it. I think, having to
> open the combo box and then beeing able to scroll in it
> is easy enough and can't happen by accident.
i actually find it extremeley useful; you have no idea how much clicking being
able to scroll through combboxes saves me in an average day =)
the biggest problem seems to be on web pages where people are scrolling the
page using the mouse and the mouse gets "snagged" in a combobox...
IMO the beauty solution would be something like this:
once scrolling a web page has started using the wheel, all wheel events
continue to scroll until the mouse has moved the manhatten length at which
point the event may be transferred to the widget beneath it (which may still
be the view).
this way, if the person is just scrolling a web page, it doesn't get snagged
up in any widget. but if they puposefully put their mouse over the widget, it
> The other problem is if you wheel mouse over konqueror's
> location bar, it will load another page. The fact is that
> changing a combobox has immediate effect, but a wheel
> mouse shouldn't change anything but the view.
the location bar in konqi should pass the scroll even through to the view,
just as scrolling on any of the other items in the tollbar does. i don't see
this alone as reason enough to labotomize all the other comboboxes. =)
Aaron J. Seigo
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43
"Everything should be made as simple as possible, but not simpler"
- Albert Einstein
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
-----END PGP SIGNATURE-----
More information about the kde-core-devel