Re: Orca help with debugging utilities

[Willie Walker <William Walker Sun COM>]

Hi Joanie:

> debug.py). These settings can be modified by adding the following lines
> to your ~/.orca/user-settings.py:
>
> debug.setEventDebugFilter(re.compile('window:activate'))
> debug.setEventDebugLevel(debug.LEVEL_OFF)

Bummer.  :-(  The docs are out of date - it's on our list to get these
up to snuff for V1.0 by Labor Day.  If you poke around in
~/.orca/user-settings.py, however, you will find a bunch of lines
associated with setting the debugLevel, eventDebugLevel, and debugFile
(which it looks like you found).

> Now when I run orca, I get a constant stream of the following which
> ultimately grinds my system to a halt if I don't stop it:
>
> vvvvv PROCESS OBJECT EVENT object:text-caret-moved vvvvv
> ^^^^^ PROCESS OBJECT EVENT object:text-caret-moved ^^^^^

D'Oh!  I added some code to add the "PROCESS OBJECT EVENT" lines to make
it easier to group sets of debug lines based upon a single event, but
didn't filter them out based upon the event filter.  :-(  I'll make a
note to filter these out.

However, the other thing that's happening here is that you've got the
debug output going to stdout, and you're probably running this from a
gnome-terminal.  When you do this, all the data being send to stdout is
causing gnome-terminal to issue more events, which are then printed as
debug output.  It's a viscous perpetual motion machine.  There are two
ways to work around this:

1) Send debug output to a file (look for the orca.debug.debugFile line
in ~/.orca/user-settings.py and uncomment it).

and/or

2) Run orca from a shell that's not in an application that knows about
the AT-SPI.  This could be a virtual console or an xterm, for example.

Hope this helps,

Will