Going crazy with closing a stack

[Doug Lerner]

That's almost what I ended up doing. Instead of running that stack as a
substack, I made it its own stack and moved all the handlers except for
openStack and closeStack elsewhere.

It seems to be working this way.

Thanks,

dogu

On 2/2/04 4:57 PM, "Frank Leahy" <frank at backtalk.com> wrote:

> Doug,
> 
> I'm guessing that other stacks of yours are getting closeStack
> messages, right?  If so then I'm pretty sure you're not getting a
> closeStack because of something you're doing.  Maybe you forgot to pass
> menuPick, or pass some other message that is keep RunRev from sending
> you the closeStack messages.
> 
> Whatever it is, at this point I'd create a new stack, place just this
> controller you're trying to use on it -- with no other scripts in the
> stack except the closeStack -- and see if a closeStack handler gets
> called.  Then add your other scripts one at a time (or a bunch at a
> time) until you see it stop getting called again.
> 
> It's great to use the list as a sounding board, but sometimes the only
> way to do debugging is to return to a zero baseline and actually do the
> debugging.
> 
> Good luck,
> -- Frank
> 
> On Monday, February 2, 2004, at 02:30  AM,
> use-revolution-request at lists.runrev.com wrote:
> 
>> Thanks for your note, Tom.
>> 
>> Unfortunately, I can't move this stuff into the startup and shutdown
>> handlers because this is just one of several stacks that are open while
>> running the app and doesn't take place at shutdown.
>> 
>> doug
> 
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/use-revolution