Hi,

I\'m using amaroK for a long time now, but there one thing I find really annoying: The DCOP commands volumeUp and volumeDown change the volume by a hardcoded value, so it\'s not possible to configure that after compiling. (You might ask, why it could be necessary. Well for instance if you use a remote control sending signals very fast the defined value of 4 is too big.)

I would suggest to either create new functions such as volumeUpBy(int step) or make the step size configurable.

For my home version of amarok I\'ve extended the DCOP interface, so if you want I could apply this patch to the SVN tree.

Johannes

You can emulate this very easily. Make a little script:

vol = getVolume()
setVolume( vol + 1 )

You\'re totally right, but if this script has to be executet very fast the interpreter has to be loaded every time and that\'s inefficient.

Furthermore harcoding such values without any (for me) obvious reason is ugly...

Johannes

Alright, added this DCOP call:

setVolumeRelative(int ticks) //Sets volume relatively by ticks.

Thanks, I will check this out.

Very well, but that doesn't solve the same problem for the normal volume slider, does it?
I'm sometimes using the slider at very low volumes as I have a headphone which is rather efficient. At very low volumes 4% steps using either the mouse wheel or W-KP_+ (weird keycombo btw., considering KP_+ alone doesn't do anything as far as I can see) are quite a lot. Of course that is a problem for any stepsize, but having a stepsize of 1% would alleviate the problem.


I.