Re: Close Substack Question?
On 4/6/06 12:20 PM, "J. Landman Gay" <[EMAIL PROTECTED]> wrote: > Let's go back to your original post: > >> I have a library stack that is opened via a start using command. This >> works fine, however if the same stack I have a sub-stack which is >> used for debugging, e.g. it has a field and dumps lines to the field. >> This works fine too, until I close the sub-stack. When I do this, it >> closes the mainStack too, so the library is "lost" to the other >> stacks that are using it. Is it possible that the library is "in use", but has not officially been opened before the substack is opened? If this is the case, then opening a substack and then closing it would actually close the whole stack... I've had that happen to me before. The way to get around it is to open your library stack invisibly after you have started using it, and then when you open and close your substack, the library stack will remain open. HTH, Ken Ray Sons of Thunder Software Web site: http://www.sonsothunder.com/ Email: [EMAIL PROTECTED] ___ 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
Re: Close Substack Question?
David Burgun wrote: > I am more confused than ever now! The whole thing is more confused > since I have most of the "open" and "close" handlers in Card 1 of the > stack(s). I still don't fully understand why I need them in Card 1, but > when I was having problems with it in the past someone told me to put > them in card 1 so I did. This is only usual for system messages that should only apply to that stack when it first opens. Scripts in the card will not execute unless that card is frontmost. If you have a one-card stack, then it is always frontmost, so the technique isn't strictly necessary in that case (but it won't hurt.) > I really would like to get this under control > and have all the handlers I need in the right places and just have it > work! Let's go back to your original post: > I have a library stack that is opened via a start using command. This > works fine, however if the same stack I have a sub-stack which is > used for debugging, e.g. it has a field and dumps lines to the field. > This works fine too, until I close the sub-stack. When I do this, it > closes the mainStack too, so the library is "lost" to the other > stacks that are using it. Closing a substack should not (and generally doesn't) close the mainstack. The only time this would happen is if you have a handler that "falls through" to one of the main stacks or libraries, which effects a "close this stack" without checking to see which stack it is actually closing. My suggestion: remove all handlers that you have inserted to try to resolve this problem. If you have any closestack or closeStackRequest handlers in your libraries, comment them out for now. You should see the behavior you want; closing one stack will not close any others when you click on the closebox. Once you get that far, if you still need help, write again. -- Jacqueline Landman Gay | [EMAIL PROTECTED] HyperActive Software | http://www.hyperactivesw.com ___ 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
Re: Close Substack Question?
Hi, On 5 Apr 2006, at 18:19, J. Landman Gay wrote: What you describe is the default behavior and you shouldn't have to do anything to accomplish it. The IDE will ask if you want to save if the stack is dirty. If you have no handlers that interfere with closeStackRequest, closeStack, etc. then your stack should act the way you want it to. There is no documentation about it because you have to actively write handlers to prevent it if you don't want that behavior. In a standalone, you would have to write the handlers that track a dirty variable and ask to save, since this is part of the IDE but doesn't exist in a standalone. For that, a closeStackRequest is the most commonly-used way to trap a click on the close box. When you are done checking the dirty status and saving the stack, pass the closeStackRequest to allow the stack to close. I am more confused than ever now! The whole thing is more confused since I have most of the "open" and "close" handlers in Card 1 of the stack(s). I still don't fully understand why I need them in Card 1, but when I was having problems with it in the past someone told me to put them in card 1 so I did. I really would like to get this under control and have all the handlers I need in the right places and just have it work! So in my setup, I have this: LibStackA:mainStack - no preOpenStack, openStack, closeStack, no closeStackRequest. One card in the mainStack, no Substacks. LibStackB:mainStack,no preOpenStack , no openStack, no closeStack, no closeStackRequest One card in the mainStack, one Substack. LibStackB:subStack1:Stack Script, preOpenStack , openStack, closeStack, closeStackRequest, no "pass" in any handler. One Card -- NormalStackA:mainStack:Stack Script, no preOpenStack ,no openStack, no closeStack, no closeStackRequest NormalStackA:mainStack:Card1 Script, preOpenStack , openStack, closeStack, closeStackRequest, no "pass" in any handler. no Substacks. NormalStackB:mainStack:Stack Script, no openStack, no closeStack, no closeStackRequest NormalStackB:mainStack:Card1 Script, preOpenStack , openStack, closeStack, closeStackRequest, no "pass" in any handler. no Substacks. What should the action be for this Setup? With it set like this, if I click close on the LibStackB:subStack1 window, I get the "Do you want to save?" dialog. I have the feeling that when I added a pass to "closeStackRequest" in my normal stack(s), it fell thru into the library stack. Do I need to test if the close was for the this stack? If so how do I do this? Would the following work: if the name of this stack <> myStackName then pass "closeStackRequest" ??? Sorry to be a pain, it's just something that I can't seem to get my head around! Once I get this straight I'm sure it will stick and I won't have to worry about it ever again! All the Best Dave ___ 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
Re: Close Substack Question?
David Burgun wrote: Hi, Ok, I tried that and now none of my stacks will close at all if i use the "close" button in the window title bar! Also the message box will not close either! Help! How do I get out of this? Is there somewhere in the docs that tell you explicitly what you need to do in order to: 1. Allow the close button in the Window Title Bar to close the window and then optionally have the "stack not saved" dialog appear? e.g. if the stack is dirty I want it to be automatically saved, 2. Have this work across many stacks and libraries. 3. Have this work with a sub-stack (my only sub-stack is in a library, but it would be nice to have a solution that works for everything!). What you describe is the default behavior and you shouldn't have to do anything to accomplish it. The IDE will ask if you want to save if the stack is dirty. If you have no handlers that interfere with closeStackRequest, closeStack, etc. then your stack should act the way you want it to. There is no documentation about it because you have to actively write handlers to prevent it if you don't want that behavior. In a standalone, you would have to write the handlers that track a dirty variable and ask to save, since this is part of the IDE but doesn't exist in a standalone. For that, a closeStackRequest is the most commonly-used way to trap a click on the close box. When you are done checking the dirty status and saving the stack, pass the closeStackRequest to allow the stack to close. -- Jacqueline Landman Gay | [EMAIL PROTECTED] HyperActive Software | http://www.hyperactivesw.com ___ 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
Re: Close Substack Question?
Hi, I have all the handlers you mention, this is my setup: LibStackA:mainStack - no openStack, closeStack or closeStackRequest, no Substacks. LibStackB:mainStack, no openStack, no closeStack or closeStackRequest LibStackB:subStack1, openStack, closeStack or closeStackRequest -- NormalStackA:mainStack:stacj no openStack, no closeStack or closeStackRequest NormalStackA:mainStack:card1 openStack, closeStack, closeStackRequest no Substacks. NormalStackB:mainStack:stacj no openStack, no closeStack or closeStackRequest NormalStackB:mainStack:card1 openStack, closeStack, closeStackRequest no Substacks. Is this correct? If so in which handlers do I need to "pass" and in which stacks/cards? Is this documented anywhere? The problem I have is that when I press the close stack button in the Window Title bar I get a dialog asking me to save the stack. If I add a closeStackRequest, I cannot close *any* window via the close button in the window title bar (even IDE stacks!). Thanks a lot Dave On 5 Apr 2006, at 17:17, Stephen Barncard wrote: you need an 'on closestack' handler somewhere in the hierarchy to close a window-stack this way if your menus or other code won't do it. This is a common conundrum when experimenting with menus. Rev allows full control of this process, but you have to write it, include all the saving stuff. This is where the message path is your friend. Hi, Ok, I tried that and now none of my stacks will close at all if i use the "close" button in the window title bar! Also the message box will not close either! Help! How do I get out of this? Is there somewhere in the docs that tell you explicitly what you need to do in order to: 1. Allow the close button in the Window Title Bar to close the window and then optionally have the "stack not saved" dialog appear? e.g. if the stack is dirty I want it to be automatically saved, 2. Have this work across many stacks and libraries. 3. Have this work with a sub-stack (my only sub-stack is in a library, but it would be nice to have a solution that works for everything!). I've searched and searched for something that explains how to do this but I can't find anything that positively tell you what should happen and how to handle it. Thanks a lot All the Best Dave -- stephen barncard s a n f r a n c i s c o - - - - - - - - - - - - ___ 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 ___ 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
Re: Close Substack Question?
you need an 'on closestack' handler somewhere in the hierarchy to close a window-stack this way if your menus or other code won't do it. This is a common conundrum when experimenting with menus. Rev allows full control of this process, but you have to write it, include all the saving stuff. This is where the message path is your friend. Hi, Ok, I tried that and now none of my stacks will close at all if i use the "close" button in the window title bar! Also the message box will not close either! Help! How do I get out of this? Is there somewhere in the docs that tell you explicitly what you need to do in order to: 1. Allow the close button in the Window Title Bar to close the window and then optionally have the "stack not saved" dialog appear? e.g. if the stack is dirty I want it to be automatically saved, 2. Have this work across many stacks and libraries. 3. Have this work with a sub-stack (my only sub-stack is in a library, but it would be nice to have a solution that works for everything!). I've searched and searched for something that explains how to do this but I can't find anything that positively tell you what should happen and how to handle it. Thanks a lot All the Best Dave -- stephen barncard s a n f r a n c i s c o - - - - - - - - - - - - ___ 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
Re: Close Substack Question?
Hi Dave, Have you tried something like this (in your "library" stack): on closeStackRequest if the short name of this stack <> the short name of me then pass closeStackRequest end closeStackRequest This should allows all other closestack requests, trapping only the one sent to your library stack. Greetings Paul Claude on 5-04-2006 14:45, David Burgun at [EMAIL PROTECTED] wrote: > Hi, > > Ok, I tried that and now none of my stacks will close at all if i use > the "close" button in the window title bar! Also the message box > will not close either! > > Help! How do I get out of this? > > Is there somewhere in the docs that tell you explicitly what you need > to do in order to: > > 1. Allow the close button in the Window Title Bar to close the > window and then optionally have the "stack not saved" dialog appear? > e.g. if the stack is dirty I want it to be automatically saved, > > 2. Have this work across many stacks and libraries. > > 3. Have this work with a sub-stack (my only sub-stack is in a > library, but it would be nice to have a solution that works for > everything!). > > I've searched and searched for something that explains how to do this > but I can't find anything that positively tell you what should happen > and how to handle it. > > Thanks a lot > All the Best > Dave > > On 4 Apr 2006, at 16:14, Rob Cozens wrote: > >> >> Dave, >> >>> I added a closeStackRequest handler to my sub-stack script: >>> >>> on closeStackRequest >>> save this stack >>> pass closeStackRequest >>> end closeStackRequest >>> >>> But I still get prompted to save the sub-stack when closing it in >>> the IDE. >>> >>> Do I need one in the mainStack too? >>> >>> >> >> I think all you need to do is not pass closeStackRequest in your >> closeStackRequest handler. >> >> Rob Cozens >> CCW, Serendipity Software Company >> >> "And I, which was two fooles, do so grow three; >> Who are a little wise, the best fooles bee." >> >> from "The Triple Foole" by John Donne (1572-1631) >> >> ___ >> 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 > > ___ > 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 > ___ 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
Re: Close Substack Question?
Hi, Ok, I tried that and now none of my stacks will close at all if i use the "close" button in the window title bar! Also the message box will not close either! Help! How do I get out of this? Is there somewhere in the docs that tell you explicitly what you need to do in order to: 1. Allow the close button in the Window Title Bar to close the window and then optionally have the "stack not saved" dialog appear? e.g. if the stack is dirty I want it to be automatically saved, 2. Have this work across many stacks and libraries. 3. Have this work with a sub-stack (my only sub-stack is in a library, but it would be nice to have a solution that works for everything!). I've searched and searched for something that explains how to do this but I can't find anything that positively tell you what should happen and how to handle it. Thanks a lot All the Best Dave On 4 Apr 2006, at 16:14, Rob Cozens wrote: Dave, I added a closeStackRequest handler to my sub-stack script: on closeStackRequest save this stack pass closeStackRequest end closeStackRequest But I still get prompted to save the sub-stack when closing it in the IDE. Do I need one in the mainStack too? I think all you need to do is not pass closeStackRequest in your closeStackRequest handler. Rob Cozens CCW, Serendipity Software Company "And I, which was two fooles, do so grow three; Who are a little wise, the best fooles bee." from "The Triple Foole" by John Donne (1572-1631) ___ 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 ___ 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
Re: Close Substack Question?
Dave, I added a closeStackRequest handler to my sub-stack script: on closeStackRequest save this stack pass closeStackRequest end closeStackRequest But I still get prompted to save the sub-stack when closing it in the IDE. Do I need one in the mainStack too? I think all you need to do is not pass closeStackRequest in your closeStackRequest handler. Rob Cozens CCW, Serendipity Software Company "And I, which was two fooles, do so grow three; Who are a little wise, the best fooles bee." from "The Triple Foole" by John Donne (1572-1631) ___ 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
Re: Close Substack Question?
On 3 Apr 2006, at 16:42, Rob Cozens wrote: Hi Dave, I have the preOpenStack, openStack and closeStack handlers defined in the Script of the sub-stack. Any ideas? A closeStackRequest handler in the main stack? I added a closeStackRequest handler to my sub-stack script: on closeStackRequest save this stack pass closeStackRequest end closeStackRequest But I still get prompted to save the sub-stack when closing it in the IDE. Do I need one in the mainStack too? Thanks a lot All the Best Dave ___ 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
Re: Close Substack Question?
Hi Dave, I have the preOpenStack, openStack and closeStack handlers defined in the Script of the sub-stack. Any ideas? A closeStackRequest handler in the main stack? Rob Cozens CCW, Serendipity Software Company "And I, which was two fooles, do so grow three; Who are a little wise, the best fooles bee." from "The Triple Foole" by John Donne (1572-1631) ___ 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
Re: Close Substack Question?
Hi Dave, I had the same problem, but only in the standalone environment. No solutions at the moment. Greetings Paul Claude on 3-04-2006 12:13, David Burgun at [EMAIL PROTECTED] wrote: > Hi All, > > I have a library stack that is opened via a start using command. This > works fine, however if the same stack I have a sub-stack which is > used for debugging, e.g. it has a field and dumps lines to the field. > This works fine too, until I close the sub-stack. When I do this, it > closes the mainStack too, so the library is "lost" to the other > stacks that are using it. > > It's no big deal since I could just "hide" the sub-stack window, but > I can't understand why closing the the sub-stack should also close > the mainStack. > > I have the preOpenStack, openStack and closeStack handlers defined in > the Script of the sub-stack. > > Any ideas? > > All the Best > Dave > > > ___ > 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 > ___ 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
Close Substack Question?
Hi All, I have a library stack that is opened via a start using command. This works fine, however if the same stack I have a sub-stack which is used for debugging, e.g. it has a field and dumps lines to the field. This works fine too, until I close the sub-stack. When I do this, it closes the mainStack too, so the library is "lost" to the other stacks that are using it. It's no big deal since I could just "hide" the sub-stack window, but I can't understand why closing the the sub-stack should also close the mainStack. I have the preOpenStack, openStack and closeStack handlers defined in the Script of the sub-stack. Any ideas? All the Best Dave ___ 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
