(*** This bug was imported into bugs.kde.org ***) Package: kdelibs Version: KDE 2.9.0 2 (3.0 beta2) Severity: wishlist Installed from: SuSE Compiler: gcc version 2.95.3 20010315 (SuSE) OS: Linux (i686) release 2.4.4-4GB OS/Compiler notes: When I first got a wheelmouse back when I was using Win9X I couldn't figure out what it was for. I tried using it to scroll scrollbars. Nope. Couldn't do dropdown lists either. Damn I couldn't even do menus! I was surprised by this. Eventually I figured that it was just for scrolling documents. In KDE the wheelmouse can do a lot of things. There are usability problems with some of these things. For example as you scroll down a web page you suddenly find you've altered a select box or started scrolling an embedded <textarea>. But the fundamental idea of being more flexible seems like a good one. I humbly suggest that you allow the wheelmouse to scroll down menubar menus. You would click on the menu to open it (I suggest allowing middle-click to open menus which appears not to be the case) then scroll down the menu with the mouse and click to choose your option. My only usability worry would be the danger of starting this by accident (as with other mousewheel behaviour). But if you have to click first to open the menu I don't see how this could happen. Less mouse movement is good. Just a suggestion. Cheers. (Submitted via bugs.kde.org) (Called from KBugReport dialog. Fields Application manually changed)
On Friday 01 March 2002 14:39 davidhj@mail.com wrote: > Package: kdelibs > Version: KDE 2.9.0 2 (3.0 beta2) > Severity: wishlist > Installed from: SuSE > Compiler: gcc version 2.95.3 20010315 (SuSE) > OS: Linux (i686) release 2.4.4-4GB > OS/Compiler notes: > > When I first got a wheelmouse back when I was using Win9X I couldn't > figure out what it was for. > > I tried using it to scroll scrollbars. Nope. Couldn't do dropdown lists > either. Damn I couldn't even do menus! > > I was surprised by this. Eventually I figured that it was just for > scrolling documents. > > In KDE the wheelmouse can do a lot of things. There are usability problems > with some of these things. For example as you scroll down a web page you > suddenly find you've altered a select box or started scrolling an embedd= ed > <textarea>. But the fundamental idea of being more flexible seems like a > good one. > > I humbly suggest that you allow the wheelmouse to scroll down menubar > menus. You would click on the menu to open it (I suggest allowing > middle-click to open menus which appears not to be the case) then scroll > down the menu with the mouse and click to choose your option. > > My only usability worry would be the danger of starting this by accident > (as with other mousewheel behaviour). But if you have to click first to > open the menu I don't see how this could happen. > > Less mouse movement is good. Just a suggestion. > Hi! Thanks for your thoughts but that won't work out. Wheelmouse events are me= ant=20 to modify the position within something ( a textfield a document whatever= ).=20 But what you suggest would be inconsistent to what the mouse cursor is mean= t=20 for. If you go to a menu with the cursor then start to scroll with the=20 wheel you would create an inconsistency between what your cursor says and= =20 where the menu is highlighted. That's just not worth it.=20 But the good news are: you can create a widget style that implements this = if you want. But it won't go into KDE if that's only change :) Greetings Stephan --=20 life is too short to make mistakes
See also: https://bugs.kde.org/show_bug.cgi?id=154515