Re: [g-a-devel]Deleting accessible objects
- From: "Padraig O'Briain" <Padraig Obriain sun com>
- To: bill haneman sun com
- Cc: michael ximian com, gnome-accessibility-devel gnome org
- Subject: Re: [g-a-devel]Deleting accessible objects
- Date: Fri, 30 Aug 2002 09:22:46 +0100 (BST)
I have been brain dead.
When a GtkWidget is destroyed its accessible, if it exists, is unreffed. This
suggests that if the accessible objects are not being deleted when at-poke is
running that at-poke is failing to unref when it is finished with them. I will
have a look at at-poke.
Padraig
[SNIP]
> >
> > Only in this sense: when an Accessible (bonobo 'at-spi' object) has a
> > positive refcount one would keep the atkobject around, decrementing the
> > refcount of the Accessible to zero should decrement the atkobject
> > refcount. I think however that the atkobject refcount should remain
> > positive while the backing widget is alive, thus I think that an
> > atkobject in the 'normal' case with a live Accessible should have a
> > refcount of two, and the acts of destroying the backing widget and of
> > unreffing the Accessible to zero should decrement the refcount. I would
> > expect that this means that the sequence of events
> >
> > widget is destroyed->atkobject state changes->client unrefs Accessible
>
>
> The idea of unreffing when the state changes to DEFUNCT is new to me. I will
see
> what impact it has.
>
>
> > would result in two atkobject unrefs.
> >
> > WHat have I forgotten? :-)
> >
> > -Bill
> [SNIP]
>
> _______________________________________________
> Gnome-accessibility-devel mailing list
> Gnome-accessibility-devel gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]