I have not done this kind of event looping yet, but couldn't you add a handler in the library that would call back that it was ready? Then in your code, do a repeat until it echoed a response?
HTH Jim Ault Las Vegas On 4/12/06 6:32 PM, "Stephen Barncard" <[EMAIL PROTECTED]> 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 _______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
