Feedback on Measure (was Re: Another pass through some basic Activity test results)

[Tomeu Vizoso]

On Mon, Sep 29, 2008 at 2:47 PM, Erik Blankinship <erikb at mediamods.com> wrote:
>
>> Do you need to do that for each window? Why don't you just listen for
>> that signal in just the main activity window and stop everything when
>> gtk.gdk.VISIBILITY_FULLY_OBSCURED and resume when otherwise?
>
>
> Full screen modes in Record completely obscure the main activity window.
>
> We don't just listen for visibility events on the video windows because
> sometimes these are fully obscured (when transcoding, for example).
>
> Therefore we listen on both the main activity window and the video windows,
> and in consultation with the activity's current state (fullscreen, normal,
> transcoding), decide if Record is the current activity.
>
> I've never fully understood the rationale for why the sugar api does not
> alert activities as to when they are active or not, thereby saving all
> activity authors these hassles.

Well, the Sugar API alerts activities when they are the active
activity (SetActive method in the dbus service), but it has a
different meaning that being visible (see my earlier email from
today). For visibility, the X stuff already provides all that is
needed and though we would like to make activity author's life as
simple as possible, properly maintaining an API is something very
expensive and we just don't have the resources for now.

Faisal's work is the best that we have right now regarding activity
author support.

Regards,

Tomeu