AW: [Gnash-commit] gnash ChangeLog gui/gtk.cpp

[Benjamin Wolsey]

----- Ursprüngliche Mail ----
> Von: Bastiaan Jacques <address@hidden>
> An: Benjamin Wolsey <address@hidden>
> CC: address@hidden
> Gesendet: Sonntag, den 10. Februar 2008, 23:32:24 Uhr
> Betreff: Re: [Gnash-commit] gnash ChangeLog gui/gtk.cpp
> 
 > is_muted() 
is 
implemented; however 
it 
appears 
the 
semantics 
have 
change.
> Also 
implemented 
from 
sound_handler 
are 
mute() 
and unmute().
> Thus, 
I reasoned, 
muted() 
should 
return 
true 
only 
if 
mute() 
has 
been 
previously
> called. 
It 
makes 
no 
sense 
to 
be 
muted 
at 
startup, unless there 
is 
a
> configuration 
option 
for 
that.

> What 
are 
the 
semantics 
of 
is_muted() 
for 
GUI 
purposes?
 

I added the check on get_muted to decide whether to set the 'Sound' checkbox to 
on or off as Gnash starts. It was a bit of attempted foresight in case a 
configurable option to start with sound muted gets added, which isn't 
implausible. No problem at the moment, though - it can be dealt with if that 
option is ever introduced.

bwy




      Lesen Sie Ihre E-Mails jetzt einfach von unterwegs.
www.yahoo.de/go