Re: [orca-list] The value for orca to have time information in the debug files

[Steve Holmes <steve holmes88 gmail com>]

Hose, you didn't reply to the list so I am bringing this back to the
list.

We already have a key that turns debugging on and off although it
rotors through several other values.  But as a variant of what you
suggest, the new hotkey could insert a message and have a counter
associated like you said.  Then to reset this counter, just rotor
through the off position with the existing hot key and you could start
with a new sequence.

I still like the ability for someone to put in custom text like a
debug label for a given series of events or something.

I originally wanted to just use a shell command to echo text
> > debug.out but when I attempted that, it didn't work.  I think Orca
was overwriting my appended message with more output.  I might even
mess with that more by changing debug levels and see if that makes any
difference.  I think the trouble is while the file is opened with
Orca, you can't come along and append text to it from another shell.
That would surely make sense.

On Wed, Nov 10, 2010 at 03:24:29PM -0200, José Vilmar Estácio de Souza wrote:
> Hi Steve and all.
>
> I imagine the following implementation:
> 1. A key to toggle debug on/off on the fly.
> 2. When the key is pressed debug is set to on/off  and the following
> message would be announced by orca and inserted in the debug file:
> debug is <status> #
> Where <status> is on or off and # is a sequence that is incremented
> each time that debug is turned on.
>
>
> On 11/10/2010 02:57 PM, Steve Holmes wrote:
> > On Wed, Nov 10, 2010 at 12:41:42PM +0000, Michael Whapples wrote:
> > > Hello,
> > > Yes I think being able to post extra messages into the debug would
> > > be useful. Remember you will get a whole bundle of events associated
> > > to the action of inserting the user message, therefore it may be
> > > worth considering how you can minimise these (e.g. might it be
> > > cleaner in the debug if it was a key stroke to insert a
> > > predetermined message rather than having a dialog open, etc).
> > Hmmm, I hadn't thought about the dialog triggering even more events.
> > I think the feature is more valuable if the user can specify the
> > message contents each time it is inserted but you're right concerning
> > the opening and closing of the Orca dialog prompting for the message.
> > The only work-around that I could see immediately being done would be
> > for the user to turn the debug level down to off, then insert the
> > message and then turn debug level back up to full or whatever
> > desired.  I would not tie the insertion message to any debug levels
> > since this is a manual thing called for by the user on demand.  I have
> > a permanent key assigned to rotor the debug levels on my setup.
> >
> > Another idea I just thought of could be to split this up and have one
> > function that just adds the user message to a flat file and then have
> > the debug insert function copy the contents of that flat file into the
> > debug output.  However in either case, this dialog interaction would
> > spiew contents into the debug out.  I suppose this functionality could
> > automatically bypass debug output temperarially while processing.
> >
> > Gee, don't wanna make this thing too complicated before it even starts
> > <smile>.
> > _______________________________________________
> > 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.
> > The manual is at http://library.gnome.org/users/gnome-access-guide/nightly/ats-2.html
> > The FAQ is at http://live.gnome.org/Orca/FrequentlyAskedQuestions
> > Netiquette Guidelines are at http://live.gnome.org/Orca/FrequentlyAskedQuestions/NetiquetteGuidelines
> > Log bugs and feature requests at http://bugzilla.gnome.org
> > Find out how to help at http://live.gnome.org/Orca/HowCanIHelp