Another suggestion to improve debugging:
I can interrupt a script with command + "." (mac). But this doesn't
work when I have an answer dialog popping on. Because on a mac an
answer dialog is in "sheet" mode, it needs to be dismissed before my
keyboard events get to influence the stack behaviour.
When in sheet mode, the menu is still accessible.... why not have an
item "interrupt script" in the "Development" menu?
Marielle
A while ago I wished that while debugging I had a stack, in the non-
Rev sense, available to examine, and so as to change debugging
context. Somebody (sorry, I've forgotten who) pointed out that we
do have that: a pulldown menu in the Message Box.
Good -- but it's usually wrong. The stack (in the Rev sense) I
need, which is the stack I'm in (using, debugging), isn't the one
auto-selected there -- that's another stack a couple of steps back.
It may be the last one *accessed* by Rev (I wrote something to it
from the current stack), but it isn't meaningfully the *current*
stack, the one I'm looking at, the one whose controls and variables
I want to access. So I keep typing stuff into the msg box that gets
errors because I'm not noticing it's paying attention to some other
stack.
------------------------------------------------------------------------
--------
Marielle Lange (PhD), Psycholinguist
Alternative emails: [EMAIL PROTECTED], [EMAIL PROTECTED]
Homepage
http://homepages.lexicall.org/mlange/
Easy access to lexical databases http://lexicall.org
Supporting Education Technologists http://
revolution.lexicall.org
_______________________________________________
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
