[Kde-accessibility] Re: Documentation about ATK and AT-SPI

[Bill Haneman]

> I did not find any documentation about AtkObjectIface. However, I do not know 
> if we need this interface as it should be possible to create AtkObjects 
> within the bridge.

You don't need it but it may be useful to you.  It provides an
alternative to creating GObjects which are subtypes of AtkObject.

> > In addition to the 'register/deregisterApplication' methods, the
> > 'notifyEvent' method is of interest to applications since either they or
> > their "bridges" must call "Registry.notifyEvent" in order to send
> > event notifications to interested clients.  Similarly the applications
> > are responsible for sending certain kinds of "key events" to the
> > registry when the application receives keystrokes - this is a method of
> > AtkUtil which is of interest to non-gtk+ applications and toolkits.
> > [...]
> I did not find any documentation about the Registry.notifyEvent method or 
> similar methods within AtkUtil. 

Right, because these methods are methods of the accessibility registry
daemon.  You will find this information in the at-spi IDL.

>From what I've read in the on-line 
> documentation I understood that the clients (or the broker) install 
> event-listeners, so such a method would not needed.

Your bridges must call the registry's notify method just as you must
call register/deregisterApplication.  Otherwise the client event
listeners won't be notified when events are sent!

- Bill

> Gunnar Schmi Dt
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.7 (GNU/Linux)
> 
> iD8DBQE++tcAsxZ93p+gHn4RAppiAKCo9oWWpnoTFUu494/Ybj2rtLpgXwCgrZ4l
> rvCMbxUAOlY+PY3cw84SF/E=
> =IEcm
> -----END PGP SIGNATURE-----
> 
>