Bug 193478

Summary:	kmix should show number-values for audio levels
Product:	[Applications] kmix	Reporter:	Mohd Asif Ali Rizwaan <maarizwan>
Component:	general	Assignee:	Christian Esken <esken>
Status:	RESOLVED DUPLICATE
Severity:	wishlist	CC:	bugzilla, josiah.barber
Priority:	NOR
Version:	3.5
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:

Description Mohd Asif Ali Rizwaan 2009-05-21 12:19:06 UTC

Version:           3.5 (using 4.2.85 (KDE 4.2.85 (KDE 4.3 Beta1)), Kubuntu packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.28-12-generic

It would be nice to have Numeric values below/beside the "slider" to visually and numerically remember sound output. Just like we have to color selection, we can slide and "give precise values" for colors. why not for sound? :)

Or, could we have % (percentage) representation below the slider. 

Bother integer and %percentage option would help us to ask others to set the volume to specific rate. 

This way we can ask anybody who might be using the pc to set the volume to 80 points or 80%. or please reduce the volume to 30%.

thanks.

Comment 1 Mohd Asif Ali Rizwaan 2009-05-21 12:20:56 UTC

Just noticed, when we hover the mouse pointer over kmix system tray icon, it shows "volume at 41%" in the tooltip.

it would be nice to have "realtime" %percentage tooltip when we slide the volume. thanks.

Comment 2 Janet 2009-09-20 15:20:50 UTC

In KDE3's kmix it was possible to show the volume as a numerical value for every mixer which was very helpful for orientation. Please readd this option for KDE4's kmix.

Comment 3 Josiah Barber 2009-10-17 10:20:37 UTC

kmix is the only KDE3 app I still use.  I consider the KDE4 version useless without the value above the slider.  The KDE3 version looks a little out of place, however, so it would be really nice to get the KDE4 version fully functional.

Comment 4 Christian Esken 2010-08-01 00:17:38 UTC

I have no time to implement that, but will gratefully accept patches for that
feature.

*** This bug has been marked as a duplicate of bug 170527 ***