focus tracking

Jos Poortvliet jospoortvliet at
Thu Jul 1 20:53:13 BST 2010

On Wednesday 30 June 2010 18:34:01 Joseph Scheuhammer wrote:
> On 30/06/10 6:02 AM, PiƱeiro wrote:
> > But, other people involved (Mike Gorse, Joanie) can confirm/complete
> > all this.
> >    
> I'll confirm:  What your wrote is a good summary of the situation.  Thanks!
> In terms of "complete all this":  GS-mag supports another route for 
> controlling its settings, namely, GConf.  Furthermore, that part of the 
> code is in the process of being converted to GSettings [1].  The idea is 
> that by changing a user's session wide magnification preferences via 
> GSettings live-updates the magnifier's settings.  A concrete example is 
> setting the mouse tracking preference in Orca's magnifier when running 
> gs-mag.  In this case, Orca uses GConf to change the user's magnifier 
> mouse tracking desktop preferences.  GS-mag "hears" that change and 
> responds appropriately.

Ok, thanks all for the responses. A couple of questions if you don't mind, to check I understand this properly:
- AT-SPI does not have a way of tracking focus for magnification purposes?
- So Gnome-Mag has developed an API for this, but it's currently CORBA based and thus needs changing
- apps need to support this API for magnification to properly work

So, if this is the case, I wonder what the plans are? At the very least having a standard developed for apps based on D-BUS which can be implemented by eg OO.o and Qt and KDE apps too, would be nice. I wonder if it's possible to make this part of AT-SPI somehow?
> A couple of related issues/tasks are that Orca's preferences [2] , and 
> desktop a11y preferences [3] are also migrating to the GSettings solution.
> [1] (Port magnifier to 
> GSettings [GnomeShell])
> [2] (Migrate to 
> GSettings [Orca])
> [3] (Speech, braille, 
> and magnification should be general desktop preferences [Orca])

More information about the kde-core-devel mailing list