go vs open?
revdan at danshafer.com
Sat Feb 7 11:26:26 CST 2004
Your questions led me to discover the problem. Thanks.
The stack in question was open, but hidden. Using "open" or "go" on a
stack that's already open won't show it and bring it to the front. You
have to "show" it.
My guess is that the condition of the stack was different (i.e., hidden
sometimes, closed others) and that's why the problem *seemed* to arise.
I decided ultimately not to hide the stack but to close it. I hope that
doesn't eventually bite me in the butt; I'm always hesitant to close
things because of my remaining uncertainty about what happens to the
stacks data and state when I do that. I guess I'm about to find out.
On Feb 6, 2004, at 10:45 PM, Jeanne A. E. DeVoto wrote:
> At 9:05 PM -0800 2/6/04, Dan Shafer wrote:
>> open stack "PIClearingNew"
>> When it executes, the stack opens fine. But the error dialog pops up
>> and tells me there's an error on that line.
>> If I change "open" to "go" it works fine and I get no error.
> They should be synonymous, but maybe there's some glitch.
> Is the stack open at the time, or closed? If open, frontmost or not?
Closed. Actually, probably more often it's open but hidden. Definitely
> Do you get the same error if you simply enter the command in the
> message box, without the surrounding script?
> What happens if you retype the word "open" into the script,
> eliminating any possibility that some weird invisible character has
> sneaked in?
> jeanne a. e. devoto ~ jaed at jaedworks.com
> use-revolution mailing list
> use-revolution at lists.runrev.com
Dan Shafer, Revolutionary
Author of "Revolution: Software at the Speed of Thought"
http://www.revolutionpros.com for more info
Available at Runtime Revolution Store (http://www.runrev.com/RevPress)
More information about the use-livecode