Re: Accessing stacks without opening
Thanks. I figured out, too, that my thinking that things were being saved in stacks I'd accessed this way was because they were still loaded into memory. When I quit and reopened nothing was there. So you need to save the stack. Still I can see where this can be handy in some situations as all the normal openCard, etc scripts are not called. Marty Marty Knapp wrote: So it appears that you can set custom properties of a stack and "put" information into fields of stacks that are not open, from a stack that is open. I just did it by accident! That being the case, is there anything that I should be aware of when doing this? Is the referenced stack loaded into memory? Is this considered bad form? As Phil said, it can be handy. I use prefs stacks this way sometimes because they're available but out of the message path. I make sure to close the prefs stack when the main stack quits. ___ 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: Accessing stacks without opening
Marty Knapp wrote: So it appears that you can set custom properties of a stack and "put" information into fields of stacks that are not open, from a stack that is open. I just did it by accident! That being the case, is there anything that I should be aware of when doing this? Is the referenced stack loaded into memory? Is this considered bad form? As Phil said, it can be handy. I use prefs stacks this way sometimes because they're available but out of the message path. I make sure to close the prefs stack when the main stack quits. -- Jacqueline Landman Gay | jac...@hyperactivesw.com 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: Accessing stacks without opening
Hi Marty, When you reference a stack that is not open, it is brought into memory. Even this will do it: -- set 'it' to true or false get (there is a stack "abc") -- looks in the default folder for the stack Or you can reference the stack by its filename. When a stack file is brought into memory this way, none of the normal preOpen / open messages are sent to it or its parts. AND visible stacks are not shown. You can definitely use this to your advantage in certain cases! It is not bad form. The important thing is that you know what's happening. Phil Davis On 4/26/10 6:47 PM, Marty Knapp wrote: So it appears that you can set custom properties of a stack and "put" information into fields of stacks that are not open, from a stack that is open. I just did it by accident! That being the case, is there anything that I should be aware of when doing this? Is the referenced stack loaded into memory? Is this considered bad form? Thanks, Marty Knapp -- Phil Davis PDS Labs Professional Software Development http://pdslabs.net ___ 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: Accessing stacks without opening
You can check to see if it is open invisibly by looking in the application browser. The application browser is worth getting to know. Using stacks that are invisible is not bad form, but you should be aware when you do it. --Original Message-- From: Marty Knapp Sender: use-revolution-boun...@lists.runrev.com To: How to use Revolution ReplyTo: How to use Revolution Subject: Accessing stacks without opening Sent: Apr 26, 2010 9:47 PM So it appears that you can set custom properties of a stack and "put" information into fields of stacks that are not open, from a stack that is open. I just did it by accident! That being the case, is there anything that I should be aware of when doing this? Is the referenced stack loaded into memory? Is this considered bad form? Thanks, Marty Knapp ___ 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 Sent from my Verizon Wireless BlackBerry___ 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
Accessing stacks without opening
So it appears that you can set custom properties of a stack and "put" information into fields of stacks that are not open, from a stack that is open. I just did it by accident! That being the case, is there anything that I should be aware of when doing this? Is the referenced stack loaded into memory? Is this considered bad form? Thanks, Marty Knapp ___ 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
