Re: [g-a-devel]State Change Notifications

[Marc Mulcahy <marc mulcahy sun com>]

OK, just committed the change to fix this.  So, the correct event to 
register for is "object:state-changed".

Sorry for the confusion.

Marc

At 03:16 PM 5/13/2002 +0100, Bill Haneman wrote:
> On Mon, 2002-05-13 at 13:27, Marc Mulcahy wrote:
> > Remus and All:
> >
> > The correct event to register for is "object:state-change" not
> > "object:state-changed" as your previous mail indicated...
>
> The API docs say "state-changed".  That is what the java bridge
> currently generates and what our test programs listen for.
>
> How difficult would it be to bring the bridge's behavior in line with
> the docs?
>
> -Bill
>
> > Due to a patch I just submitted, you can now register for specific state
> > change notifications,.  For example, you can register for:
> >
> > "object:state-change:checked"
> > "object:state-changed:focused"
> > etc.
> >
> > The first detail is 0 if the state is being cleared, 1 if it is being
> > set.  So, if you register for the generic state-change event, you can do
> > comparisons on the last part of the event type to tell what state  has
> > changed.  To make the string comparisons more efficient in this case, you
> > may wish to  use the GQuark stuff.
> >
> > Regards,
> >
> > Marc
> >
> > _______________________________________________
> > 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