openStack Initialization Issues

[Devin Asay]

On Feb 26, 2006, at 11:14 PM, Arthur Urban wrote:

>
>
> Richard Gaskin wrote:
>> Arthur Urban wrote:
>>> Is there a way I can detect when my main stack receives the  
>>> openStack message versus when my substacks receives the message  
>>> and pass it all the way down to the mainstack? I do once only  
>>> initialization in my mainstack, and I can't seem to reliably  
>>> detect when a substack is triggering the openStack message and  
>>> skip over the init code. I've tried using the target and the me  
>>> function, nothing seems to work. Too bad there is no  
>>> openMainStack handler. (even using on startUp doesn't help me)  
>>> Ugh...what am i missing? thanx!
>>
>> If you put your mainStack's initialization into the card script of  
>> your mainStack you never need to worry about substacks triggering it.
> That sure is mighty clever...I might even have to do that. I'm  
> surprised that there is no "official" and "correct" way to deal  
> with this, but perhaps as more folks see this thread, a non- 
> workaround might arise. Thank you so much for the input! :)

Don't forget the good ol' startup message handler, which executes  
when you first launch, although that only works when you compile the  
stack as a standalone. It's not terribly helpful when you're working  
in the development environment.

Devin

Devin Asay
Humanities Technology and Research Support Center
Brigham Young University