startup question

[Chipp Walters]

Stephen,

Regarding my last comment, I may have addressed a problem you didn't have.

You could have a callback message sent after the library has loaded, and 
trap it in the stack, then resume your startup code there, of course 
your openStack and other handlers would've already run.

You might try 'wait 30 ticks with messages' and see if it doesn't help.
Just an idea.

best,

Chipp

Stephen Barncard wrote:
> I have a chicken-and-egg situation..
> 
> I have a stack startup handler that works fine until it does a 'start 
> using' for a library stack, and then immediately needs to use a handler 
> in that stack just included.
> 
> What happens is that the code keeps marching along, the lib isn't active 
> yet... and --- error.
> 
> I've put a 'wait 30 ticks' then a 'wait 60 ticks' before continuing. Not 
> long enough? I know, I know, cheesy too.
> 
> What's the best way to allow the lib to load.. and how do I wait or hold 
> for it?
> I know there's an 'librarystack' message..
> 
> thanks.
> 
> sqb