Re: [g-a-devel]Detecting opening and closure of dialogs using CSPI

[Marc Mulcahy <marc mulcahy sun com>]

I'm going through a week's worth of email, so pardon if this is duplication...

I agree with Michael here-- it would be useful to have the ability to 
listen to children-changed only on a specific object.  Listening for it on 
all objects would seem to be a nightmare.

Marc

At 06:01 PM 3/18/2002 +0000, Michael Meeks wrote:
> Hi Guys,
>
>         This children-changed thing worries me.
>
> On Sat, 2002-03-16 at 15:58, Mukund wrote:
> >       parent = Accessible_getParent (event->source);
> >       if (!parent)
>
>         This suffers from several problems:
>
>         * an exception will return a NULL parent
>         * children-changed is fired for accessibles that will be
>           destroyed soon - causing a race nightmare (perhaps)
>         * the parent of an application should be a desktop not NULL
>         * the performance issues here are just horrible,
>                 + we get notified of all children changes
>                 + for each we do a roundtrip to the remote process
>
>         When we implement the 'listenForEventOn' I think we should allow the
> API to listen for events on a single accessible, and or on an
> accessible's children, otherwise we're going to see loads of listeners
> getting all these events and then doing expensive round trips to try and
> work out where in the tree they are. IMHO not a good thing.
>
>         Hmm,
>
>                 Michael.
>
> --
>  mmeeks gnu org  <><, Pseudo Engineer, itinerant idiot
>
> _______________________________________________
> Gnome-accessibility-devel mailing list
> Gnome-accessibility-devel gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel