basic question about "go to stack" and scripts in that stack

[william humphrey]

It wasn't a bug just another thing i didn't understand. The script in
question was in the card script of the stack not the stack script. So even
though I would go to the specific card it still didn't work and for some
reason only works if you are on that card by clicking on it.
Moving the scripts to the background of the main stack solved the problem as
you pointed out those scripts work from any card in any substack of the main
stack.

It is still unexpected behavior to me that "go to card testscripts of stack
mainstack" isn't the same thing as clicking on it with your mouse.

On Mon, Sep 1, 2008 at 2:47 PM, william humphrey <shoreagent at gmail.com>wrote:

> Thank you. That is the behavior I expected and was not getting. So my next
> step is to try to figure out if this is a bug of the beta version although I
> don't think so ...
> I will make a simpler version of my two stacks and test it. I really wish
> that the day would have more hours in it...
>
> On Mon, Sep 1, 2008 at 1:50 PM, J. Landman Gay <jacque at hyperactivesw.com>wrote:
>
>> william humphrey wrote:
>>
>>> This is a simple question.
>>> If you have two stacks (one is a substack of the other and both are side
>>> by
>>> side on my monitor) and you click on one stack manually with the mouse
>>> then
>>> the scripts in that stack all work perfectly but if you "go to that
>>> stack"
>>> with a script from the other stack the scripts do not work  even though
>>> visually it appears that the stack is active in front of you and
>>> selected.
>>>
>>
>> Generally you don't have to do anything, the stack you go to becomes the
>> defaultstack. But in some cases that doesn't happen, and you need to set it
>> yourself: set the defaultstack to <firstStack>.
>>
>> Another option is to simply put the function into the main stack script.
>> All substacks can use them from there.
>>
>> --
>
>


-- 
http://www.bluewatermaritime.com