https://bugs.kde.org/show_bug.cgi?id=34362 --- Comment #40 from rickst29 2011-11-22 23:43:38 --- (In reply to comment #38) > I also think this is not the solution but supporting more hardware buttons is > part of another limitation. > Let's imagine a user who has a mouse with "forward-backward" buttons on it and > a keyboard also with forward an backward buttons. Neither of them work. > Many other apps (browsers and e.g. the ubuntu software center) don't need > special configuration for these keys, they just work. It would be also not > appropriate to have to configure this, since the buttons have a strict meaning > on them. > The best thing would be just support all "special" buttons side-by-side to what > you configured. I guess the scancodes are standardised. > I don't want to be rude but I guess neither of the devs has a mouse or keyboard > with "forward-back" buttons. Hi, Michael! There are a lot of comments about this, but you don't need to read them all- I wasted MY time for you, so you get only the 'executive summary' ;) Here, among the KDE people, we strongly agree that 'BackButton' and 'ForwardButton' are widely recognized and used for those purposes. The current names, 'XButton1' and 'XButton2' are cryptic and non-obvious. So, if you look at the actual code in Comment 34, you see that I created new alias names for those buttons. Following the change to make the button identity obvious to other Developers, our process calls for bugs to be written against the specific programs- not the entire Kdelibs (or Qt, as it ultimately turned out to be.) Konqueror is one of those programs, obviously. File browsers- Krusader and Dolphin together with most any FileChooser pop-up (the code is shared) are another obvious candidate. And Amarok is another: Go "back" to the Previous Track or Scene in the album/movie. But I won't be writing that code- it gets managed within those specific projects. Different Product == Different Bug. BTW, my initial reason for doing this was "feature-parity" with GTK+ (the Qt-like library underneath Gnome-2) and the Compiz Window manager. I have had the EXACTLY the same opinion which you have, and our 1419 other voters. Since KDE 4.8is frozen for "new features in the API", you won't be seeing this in the near future. But KDE-Next, in 2012, will have it all. BTW, did you just offer to buy me a Razr Naga? If so, I prefer the "molten" look. My current mouse (Logitech 700) has only 14 buttons, and I'm including the 4 tilt wheel directions in that count. Need Razr! < /joke > -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.