[PATCH powerd] audio inhibit support
walter.bender at gmail.com
Tue May 22 12:45:11 EDT 2012
On Tue, May 22, 2012 at 9:12 AM, Gary Martin <garycmartin at googlemail.com> wrote:
> Hi Walter,
> You might also want to take a quick look at what Physics is doing, might not
> be pretty, but I remember needing to catch more than one event/test to make
> sure the simulation was suspended correctly across a range of past build
> releases, perhaps also a case where switching to a desktop view vs. another
> activity needed to watch for a different event.
What I found was that notify::action was enough to catch most of what
I needed. At first I didn't think it was working properly because I
wasn't seeing the signal when switching from Measure to the Desktop.
But as soon as I switched to a different activity, I see the
notification. So unless the Desktop (or Journal or Neighborhood) need
to access gstreamer, I think we are OK.
> On May 21, 2012 1:44 PM, "Walter Bender" <walter.bender at gmail.com> wrote:
>> On Mon, May 21, 2012 at 6:44 AM, Sascha Silbe <silbe at activitycentral.com>
>> > Walter Bender <walter.bender at gmail.com> writes:
>> >> On Sun, May 20, 2012 at 7:00 PM, Sascha Silbe
>> >> <silbe at activitycentral.com> wrote:
>> > [...]
>> >>> - Turtle Art v138
>> >> For TA, this is by design: if you are recording data, you want to keep
>> >> recording even when in the background. Same goes for Measure.
>> > Ah, should have noted exactly what I tested for each Activity. For
>> > Turtle Art (wasn't that Turtle Blocks at some time? still confused) that
>> > was only playback, not recording.
>> >> For playback it should release the device.
>> > I agree, for Turtle Art it will usually be the right thing to do when
>> > switching to a different Activity. Jukebox OTOH would be a good example
>> > of an Activity that should continue playback even in the background (but
>> > close the device as soon as it's finished playing).
>> > Sascha
>> > --
>> > http://sascha.silbe.org/
>> > http://www.infra-silbe.de/
>> I see that Clock is using notify::active and then checking
>> self.props.active. In Turtle Blocks, I had been using
>> visibility-notify-event. Is the former recommended? More reliable?
>> Walter Bender
>> Sugar Labs
>> Devel mailing list
>> Devel at lists.laptop.org
More information about the Devel