Re: [g-a-devel] at-spi2 first impressions

[Li Yuan <Li Yuan Sun COM>]

Oh, I just noticed that application-removed is used in at-spi-registryd
internally. So we only need children-changed here.

Li

On Mon, 2010-01-04 at 16:17 -0500, Willie Walker wrote:
> Hi Li, Mark:
> 
> Orca currently listens for object:children-changed events to determine when applications are removed from the desktop.  We could listen for application-removed, though (I didn't know about this event).
> 
> Will
> 
> On Dec 17, 2009, at 9:34 PM, Li Yuan wrote:
> 
> > Hi Mark,
> > 
> > Yes, for 3, probably just notify children-changed and
> > application-removed is enough. But we need ATs developers to confirm
> > this.
> > 
> > Li
> > 
> > On Thu, 2009-12-17 at 14:20 -0800, Mark Doffman wrote:
> >> Hi Li,
> >> 
> >> Looking at what is performed in the exit_func called by g_atexit i'm
> >> wondering how much of it we really need to do. (For the D-Bus case).
> >> 
> >> The exit_func:
> >> 
> >> 1) deregisters the atk event listeners.
> >> 
> >> 2) deregisters from the registryd.
> >> 
> >> 3) sends out the 'deactivate' and 'destroy' signals for each of the
> >> applications windows.
> >> 
> >> 1 & 2 are probably not necessary, the registryd, in the D-Bus, case will
> >> deregister the application when the D-Bus connection goes down.
> >> 
> >> The only issue is number 3. How reliant are AT's on the 'destroy' and
> >> 'decativate' events being sent? We could always send something similar
> >> directly from the registryd, although a children-changed on the root
> >> object will already be sent.
> >> 
> >> Thanks
> >> 
> >> Mark
> >> 
> >> On Wed, 2009-12-09 at 16:03 +0800, Li Yuan wrote:
> >>> I think gtk_quit_add is a possible fix. But if an application calls the
> >>> second gtk_main after the first one quits, the application will become
> >>> inaccessible.
> >>> 
> >>> Li
> >>> 
> >>> On Mon, 2009-12-07 at 23:40 -0500, Matthias Clasen wrote:
> >>>> Here is another observation, from looking at the code:
> >>>> 
> >>>> the atk-adaptor in at-spi2-atk inherited a horrible misfeature from
> >>>> at-spi's atk-bridge: it uses atexit to do 'cleanup' at exit. This is
> >>>> causing the most  painful problems, see
> >>>> https://bugzilla.redhat.com/show_bug.cgi?id=537843
> >>>> 
> >>>> As Owen eloquently puts it there: just say no to atexit,
> >>>> deregistration needs to be automatic regardless whether the process
> >>>> crashes or exits orderly.
> >>>> 
> >>>> 
> >>>> Matthias
> >>>> _______________________________________________
> >>>> Gnome-accessibility-devel mailing list
> >>>> Gnome-accessibility-devel gnome org
> >>>> http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
> >>> 
> >>> 
> >> 
> >> 
> > 
> > 
> > _______________________________________________
> > Gnome-accessibility-devel mailing list
> > Gnome-accessibility-devel gnome org
> > http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
>