Stacks getting 'disconnected'
In the process of trying to make an answer dialog (plan b), I ran across another problem. When opening a new window/sub-stack, does this automatically 'stop using' other stacks? When I closed this new sub-stack, somehow the connection to a library was stopped. Do I have to always define the 'default stack' every time?? thanks sqb ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
RE: Stacks getting 'disconnected'
Hi Stephen, Plan c is always an option in RunRev. But first check if you didn't forget to pass an event... Stackinuse is in use by the stack that calls it normally Then they are part of the event hierarchy in that order of calling. if stack a uses stack b's script stack c (not a substack of stack a) cannot see stack b's scripts. That's the theory. Front or Backscript are sometimes necessary. They are always present in the event queueu (front/before or back/after) you stack's events. Beware of frontscripts though... cheers Xavier -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stephen Barncard Sent: Monday, May 02, 2005 20:23 To: How to use Revolution Subject: Stacks getting 'disconnected' In the process of trying to make an answer dialog (plan b), I ran across another problem. When opening a new window/sub-stack, does this automatically 'stop using' other stacks? When I closed this new sub-stack, somehow the connection to a library was stopped. Do I have to always define the 'default stack' every time?? thanks sqb ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Stacks getting 'disconnected'
On 5/2/05 1:22 PM, Stephen Barncard [EMAIL PROTECTED] wrote: In the process of trying to make an answer dialog (plan b), I ran across another problem. When opening a new window/sub-stack, does this automatically 'stop using' other stacks? When I closed this new sub-stack, somehow the connection to a library was stopped. Do I have to always define the 'default stack' every time?? Steve, check your closestack and openStack handlers in your main stack... these can be triggered by substacks that open/close if the substack itself doesn't have its own openstack/closestack handlers. And if you're intention is to stop using other stacks when the mainstack closes, closing a substack might accidentally trigger this effect. If this is the problem, several methods exist to solve the problem: 1) Put your openstack/closestack/etc. messages in the first card of the main stack, not the mainstack itself. This will trigger properly when the mainstack closes, but is not in the message hierarchy when substacks close. 2) Put explicit openstack/closestack/etc. handlers in your substacks, even if they are stubs (i.e. on openstack/end openstack). 3) Leave the handlers in the mainstack's stack script, but use this if: on message if the owner of the target is me then -- do your mainstack-specific stuff here else pass message end if end message If this is *not* the problem, you can ignore everything I just told you. ;-) Ken Ray Sons of Thunder Software Web site: http://www.sonsothunder.com/ Email: [EMAIL PROTECTED] ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
