On Fri, Mar 28, 2008 at 01:49:49PM +0000, Michael Whapples
wrote:
> How can I tell where a bug is coming from? Some
examples of this might
> be:
> In eclipse when it does some code completion (eg.
showing the parameters
> for a method) orca does not speak or produce braille
for this bit of
> code. Is it orca, or is it the accessibility
information in eclipse?
If you enable Orca debugging, the log file will contain all
of the details of
the objects and events provided to Orca by the application
via AT-SPI. That
way, you can find out what is being disclosed to Orca
through the
accessibility API.
The disadvantage of this method is that the log files are
enormous. However,
the braille and speech output are also logged, which should
make it easier to
find the parts of the interaction that are relevant to your
problem.
The Orca wiki provides instructions on how to enable debug
mode. It's easy:
just uncomment three lines in your ~/.orca/user-prefs.py
file.
Of course you can change the name and location of the output
file if you wish.
_______________________________________________
Orca-list mailing list
Orca-list gnome.org
http
://mail.gnome.org/mailman/listinfo/orca-list
Visit http://live.gnome.org/Orca
for more information on Orca
|