Doesn't react to System's volume status

8 views
Skip to first unread message

KenBW2

unread,
Jun 17, 2007, 3:20:27 PM6/17/07
to Google Gadget: VolumeControl
The VolumeControl gadget is really good IMO - it just has one problem.

I have volume buttons on my Microsoft keyboard, but the gadget doesn't
react to this. I have also used the Sound Energy Volume Control (The
Red Bull one), and this does react. The reason I don't like that one
is because it's so damn huge.

Would it be possible to make this VolumeControl gadget react to the
System's volume control status, rather than simply controlling it?

Thanks in advance

Benjamin Schirmer

unread,
Jun 17, 2007, 4:37:10 PM6/17/07
to Google Gadget: VolumeControl
Hi,

thank you for letting me know. I do not think I can make it react in
real-time but I can make it adjust itself on a regular basis like
every 5-10 seconds.
A more frequent check could decrease performance of the sidebar
itself.

Would that be good enough?

Greetings,
Benjamin

Benjamin Schirmer

unread,
Jun 17, 2007, 4:50:31 PM6/17/07
to Google Gadget: VolumeControl
I have uploaded a file called VolumeControl_refreshBeta.gg to this
group. It currently uses a 2.5 second refresh time because 5-10 was a
bit too long.
Please let me know if this works as you want it to.

On Jun 17, 10:37 pm, Benjamin Schirmer <codename.mat...@gmail.com>
wrote:

KenBW2

unread,
Jun 17, 2007, 5:37:58 PM6/17/07
to Google Gadget: VolumeControl
Thanks very much for your very quick reply!

I'll download the gadget and see if it is good enough, but I'm sure it
will be. It just bugged me that if I changed the System's volume
elsewhere, then later changed the gadget's, I'd get deafened :p

Is this likely to be the way that the Red Bull gadget works, as this
doesn't seem to impede performance, and reacts pretty much instantly.

I'll post again, letting you know how it goes.
Thnaks again

On Jun 17, 9:50 pm, Benjamin Schirmer <codename.mat...@gmail.com>

Benjamin Schirmer

unread,
Jun 17, 2007, 5:49:17 PM6/17/07
to Google Gadget: VolumeControl
The Red Bull gadget is using the older gadget API. With the older API
it is easier to get responses from the system since it is basically
like a seperate application running within the sidebar. With the new
API the gadgets have to pull the information they need. Since I cannot
use the new fancy drawing options in the older API I am using the new
version. This has however this small drawback but I think with a timer
that is not too intrusive the delay is acceptable.

KenBW2

unread,
Jun 17, 2007, 6:17:49 PM6/17/07
to Google Gadget: VolumeControl
This is another reason I prefer your gadget - it just fits better with
the sidebar. The Red Bull one gives a huge white box, which doesn't
look to pretty to say the least.

I've tried the gadget, and the added feature is great! There doesn't
seem to be any lower performance - it could even be reduced to 1
second (unless this goes against your better judgement).

However, one major bug. It reduces the System's and gadget's volume
bit by bit till it reaches mute, which obviously isn't a good thing.

Hope this is fixable

On Jun 17, 10:49 pm, Benjamin Schirmer <codename.mat...@gmail.com>

Benjamin Schirmer

unread,
Jun 17, 2007, 6:29:42 PM6/17/07
to Google Gadget: VolumeControl
I'm happy you like it. That is exactly the reason why I chose the new
API.

There is no official guideline on how many and what intervals to use
but I try to keep the interval as high as possible without making the
gadget feel unresponsive.

The mute bug is something I cannot reproduce. Clicking on the speaker
icon in the gadget will set the system-wide "mute" without any changes
to the volume. Can you give me some steps to follow that will always
reproduce the bug ? If I can reproduce it I can find it and fix it ;)

Benjamin Schirmer

unread,
Jun 17, 2007, 9:04:39 PM6/17/07
to Google Gadget: VolumeControl
I could reproduce the problem and fixed it. I have uploaded a file
VolumeControl_refreshBeta2.gg to the group. Please let me know if this
fixes the problem for you too.

Best regards,
Benjamin

On Jun 18, 12:17 am, KenBW2 <Ken...@gmail.com> wrote:

KenBW2

unread,
Jun 18, 2007, 4:22:32 AM6/18/07
to Google Gadget: VolumeControl
Yep - seems to work great! :D

Thanks very much for your help on this - it's the only reason I wanted
to switch back to the other one, but this one is all i need.

Just out of curiosity, why would adding a timer make it reduce the
volume?

Thanks again

On Jun 18, 2:04 am, Benjamin Schirmer <codename.mat...@gmail.com>

Benjamin Schirmer

unread,
Jun 18, 2007, 10:55:18 AM6/18/07
to Google Gadget: VolumeControl
Thats great. Now I can release the new version on the website.

Every time the timer triggered it reads the current volume and sets
the slider. The slider sets the system volume when he is changed. But
somehow when the gadget was too narrow it lost accuracy and so every
time the slider was set he had a slightly smaller value. Since the
slider set the system volume the timer would read the new slightly
smaller value at the next interval and so it would go on until it was
at 0. I will now only change the slider if the volume changed at least
2 points so that this will not happen.

Reply all
Reply to author
Forward
0 new messages