On 5/26/05 1:12 PM, "Howard Bornstein" <[EMAIL PROTECTED]> wrote:
> On 5/25/05, J. Landman Gay <[EMAIL PROTECTED]> wrote: > >> The defaultstack may not be what you think it is, for example, so maybe the >> message >> is being sent somewhere unexpected and the new stack never sees it. > >> >> Try putting a button in your test stack that sets the defaultstack to >> the current test stack before you try to quit. Any luck with that? > > I put : > on openstack > set the defaultstack to me > end openstack > > in the main stack and > > on openstack > set the defaultstack to "Quit Test" > end openstack > > In the second stack. It didn't help. No, you have to set the defaultstack just before you try and quit (i.e. the line just before the quit call); defaultStack reverts to the topMost non-palette stack at idle so doing it on openstack doesn't do anything. >> One way to test without having to build an app is to suspend the >> develpment environment (from the Development menu.) That won't make >> tracking the problem any easier, but it saves you some trouble >> rebuilding a lot of standalones. > > Hmmm. I'm not sure I see the advantage. I'd have to restart Rev each > time it quit, and that seems to take longer than building standalones. > :-) Ken Ray Sons of Thunder Software Web site: http://www.sonsothunder.com/ Email: [EMAIL PROTECTED] _______________________________________________ use-revolution mailing list [email protected] http://lists.runrev.com/mailman/listinfo/use-revolution
