But if you put the closeStack in the background script of the main stack then you're back to the original problem. It gets called when you close one of the substacks.
I notice it is working OK but it may be because that first card is always open when the program is open (it's the central part of the interface) but your comment makes me worry about the functionality of closeStack for other users. On Tue, Nov 10, 2009 at 6:05 PM, Robert Brenstein <[email protected]> wrote: > On 09.11.09 at 12:48 -0400 william humphrey apparently wrote: > >> Thanks for everyone's replies about openstack message confusion. Putting >> the >> openstack (as well as closestack) items in the first card of the mainstack >> solves everything and I think it is something I used to know along with a >> myriad of other knowledge my gradually dying brain cells once contained. >> But >> now the information is in this great searchable resource. >> > > Warning: putting closestack on the first card may not always work as > expected -- that handler won't get called if the stack is closed while user > displays a non-first card. In other words, a multi-card stack should have > closestack on the stack level unless its functionality pertains only to the > first card. > > Robert > > _______________________________________________ > use-revolution mailing list > [email protected] > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-revolution > -- http://www.bluewatermaritime.com _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
