Summary: | kmix applet - ability to specify the percentage of the volume changed when spinning the mouse wheel | ||
---|---|---|---|
Product: | [Applications] kmix | Reporter: | johnelliottmartin |
Component: | general | Assignee: | Christian Esken <esken> |
Status: | RESOLVED DUPLICATE | ||
Severity: | wishlist | CC: | greatbunzinni, jussi, linux, mail |
Priority: | NOR | ||
Version: | 1.90 | ||
Target Milestone: | --- | ||
Platform: | Mandrake RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
johnelliottmartin
2002-09-22 03:25:00 UTC
I do not want to put too many configuration options in KMix. I understand your wish, but I have to think about a consistent concept before adding lots of configuration options. Please don't expect a change in KDE3.2. Chris *** Bug 58542 has been marked as a duplicate of this bug. *** Moving bug/wish to confirmed" state. Scheduled for after KDE3.2. Chris I dont know if that would be the same functionality - but i'd like to be able to assign a percentual value to my increase/decrease hotkeys also. I think this would be of interest for people using multimedia keys on keyboards to control the volume. At the moment, i find the resolution for setting the volume via hotkeys not satisfying. regards Markus Over-configurability anyone? ;-) It may be over-configurability for some, but I'm running my soundcard into a 360-watt amplifier. One click too many and it gets LOUD. Markus, what hot-keys are you talking about? Thanx. Bearcat *** Bug 121231 has been marked as a duplicate of this bug. *** This looks like a KDE4 feature (most likely KDE4.1). I am planning to make a joint setting for both mouse wheel and keyboard shortcut. This would be a nice feature for people using laptops with volume control hotkeys. For me, the volume goes from too quiet to too loud in 2 steps. So to be usable for me, the sensitivity needs either to be configurable, or the default volume step much smaller. Done. Please ee https://bugs.kde.org/show_bug.cgi?id=189995#c2 for details. *** This bug has been marked as a duplicate of bug 189995 *** |