--- "J. Landman Gay" <[EMAIL PROTECTED]> wrote:
use the Plugins feature. To do that, create a stack and put all your custom handlers into the stack script. Include a preOpenStack (or an openStack) handler on the first card that puts the stack in use. Save the stack into Revolution's Plugins folder. Then restart Revolution and choose your plugin stack from the Development->Plugins->Settings menu. Set your stack to load every time Rev starts up.
The next time you launch Rev, it will automatically open your plugin stack. The plugin stack's preOpenStack handler will put it in use. This effectively creates a library that will be accessible all the time, just as HC's home stack script was.
thanks Jacquie, very succinct. are there any caveats about saving plugins as you alter them?
I'm also interested in this technique but I haven't tried to use it yet - however it looks from the above as if it only works in the IDE rather than in a standalone, or do I misunderstand this? I guess this is not the way forward if I want to have a library which is accessible to the mainstack and other stacks further down the hierarchy in a standalone: instead I guess I need to employ the 'start using' construct as described in Richard G's recent paper, but that leaves me slightly puzzled as to whether the library stack(s) can be in a separate file from the mainstack and substacks of my actual application.
I guess this has been discussed many times before, but I am still vague on this last point. I guess that since there is only one copy of the engine running at any time, then the engine 'knows' about all .rev files which have been loaded whether they are part of a mainstack-substack cluster or are just freestanding - is this right?
Slightly muddled
Graham
--
-------------------------------------------------------------------
Graham Samuel / The Living Fossil Co. / UK & France
_______________________________________________
use-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/use-revolution
