Jeanne A. E. DeVoto wrote: >> What is the advantage of inserting backscript as opposed to just >> start using? Aside of course from the difference that I can insert >> script of any object as a backscript. > > That's pretty much it. In a plugin, the natural place for the > openStack handler is in the stack script, and if you start using the > plugin stack, you need to put a little extra logic into the openStack > handler to make sure it doesn't run every time any stack is opened > (because it's going to be in the message path, if you start using > it). Putting the library code in a button instead sidesteps the whole > issue.
Alternatvely, for libraries you can put all UI-related stuff like openStack handlers in the card script, safely outside the message path of other stacks. -- Richard Gaskin Fourth World Media Corporation Developer of WebMerge: Publish any database on any Web site ___________________________________________________________ [EMAIL PROTECTED] http://www.FourthWorld.com _______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
