Jim Ault wrote:
If there is an error window displayed when you start a script, and that
window is hidden behind another, then it stays behind. On the Mac (Panther
or later I believe) you can use Exposé to show the windows the app or all
windows of all apps.
In this case, clicking on the error dialog thumnail will let you see the
buttons and click them.
Try this with any script that runs long enough to use cmd-. to see if this
works in your case.
I'm pretty sure there was no error window open when I started. My work
flow (after the first freeze-up) was: restart Rev, open the stack, edit
a script (leaving the window open in the background,) click a button,
freeze, force-quit. I'll check again though. Good idea about Expose.
--
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
