With the COMPOSITE patch to change to full screen magnification you just need to set the zoom region viewport to the screen size. The mouse-tracking is implemented by the server (orca/gnopernicus) calling the setROI method. I don't think that any of these must be added to the PropertyBag.

These are interesting suggestions but I agree with Carlos.

Mouse tracking *might* be something we could justify adding to the propertyBag, but the end results are always going to be better when gnome-mag is directed by some other client such as gnopernicus, orca, or LSR.  If we make mouse tracking an "official" part of the API (at the moment it is only a command-line option for the 'sample implementation'), then we'd be under some pressure to make it "work better", and I am not sure that is a good idea; it would then bring in the issues of "what kind of mouse tracking", push vs centered mode, etc. which we have intentionally left to the client up to now.

Unless you want to make a detailed case for one of the above, George, I propose we close this as WONTFIX.

I guess there are work arounds, but I like the idea of a clean API approach.  I can live with WONTFIX.

Hi George - Just a last comment to help explain my reasoning for not including "follow mouse" in the propertybag.  We feel that the mouse tracking logic best belongs in the AT client, which has its own model of the 'correct' tracking behavior; further, a client may be listening to AT-SPI focus events, etc. so that it can be much smarter than a "mouse only" tracking model... and rather than build a client into the gnome-mag codebase, we felt any effort in that direction should go into the more full-featured AT frameworks.  We provided a simple mouse-following option for testing and for quick-and-dirty low-mag-factor use, but never intended it to be the primary mode of operation.

From that point of view, you can see that if a client has access to the PropertyBag interfaces, it also has access to SetROI, thus any client that could make use of PropertyBag should be doing the tracking itself.  Adding the "mouse follow" property to PropertyBag would only obscure the above intention and probably act as a bug attractor.

Thanks Carlos, for closing this bug.

Best regards

Bill 

I am pretty new to ORBit, but isn't there something to say about bandwidth?
Is it really optimal to have a client send so many setROI()s a second?