just noticed another potential bug

[Jim Ault]

On 2/5/07 8:54 AM, "Stephen Barncard" <stephenREVOLUTION at barncard.com>
wrote:
> I've seen this in 2.7.5 beta 1 and filed a Bug report. Confirmed by Marcus.
> http://quality.runrev.com/qacenter/show_bug.cgi?id=4054
> 
>>On 2/5/07 1:58 AM, "David Bovill" <david at openpartnership.net> wrote:
>> Confirmed here - in general commandkey short cuts can stop working all
>> though they continue to work direct from the menu.
>> 
Thanks for this note Stephen.  Good to hear some feedback that the bug is
actually getting attention.
I am going through a couple weeks of intense script editing.  For whatever
reason, I can only go for 15-20 minutes before the shortcut-bug gets me, and
I have to remember to use the contolkey workaround.  This used to be a rare
occurrence.

I would really like to know if there is a workaround by editing one/or more
of the rev IDE stacks because it would be at the top of my to-do list. Not
only is it counter-productive, but you have to wonder what else is going
wrong that you cannot see.

Side note:  No other program I work with has shortcuts that fail, even when
Rev is missing the beat.  The only real cure is to quit and relaunch...
since this is important software I am writing, I suppose I should quit when
it first occurs rather than trust the IDE.

To emphasize: I have *not* seen any problems with my apps but have seen
weird changes occur in the revErrors stack and the variable watcher stack.
This should be a warning to me that it could also occur in one of my stacks.
For now, frequent relaunching of Rev.

Optimistically looking forward to a fixed version.  Unfortunately I don't
have any free hours in my day for the next month or two to do any beta test
work.

Jim Ault
Las Vegas