Ken Apthorpe wrote:
Thanks all for your advice. Here are the freeze symptoms:
The mouse cursor doesn't freeze;
RR main menu does not respond to show pulldowns, keyboard commands (like
C-save/quit) don't work;
None of the tools in the toolbar respond to clicks;
In open RR windows and palettes the close-minimise-maximise buttons turn
white and don't work, and those that are not dimmed don't work;
Open windows and palettes can't be dragged around, or brought to the front;
None of the palettes respond to selection clicks.
From what you say it could have been a dysfunctional script, as the debugger
was reporting (yet another..!) error when the freeze happened.
I agree with Mark, this sounds exactly like what happens if you ignore
the error dialog. The error dialog is modal and won't allow any other
actions to take place until you deal with it. You have to hit one of the
three buttons before you can go on.
If you hit the Script button, it will take you to the line in the script
that is causing the error. If you hit the Debug button, it will not only
take you to the line, but allow you to debug and see the current values
in the Variable Watcher. If you hit Ignore, it doesn't do anything
except allow you to go back into active working mode.
Unfortunately, it is possible to click on a script window and bring it
to the front (sometimes covering the dialog). But after that, you're
blocked and it looks like a freeze. Move the script window out of the
way if that happens and click on one of the error dialog buttons to
continue.
--
Jacqueline Landman Gay | [EMAIL PROTECTED]
HyperActive Software | http://www.hyperactivesw.com
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
