2010/1/27 J. Landman Gay <[email protected]>: > Thanks. It won't work for my stacks, they have too many cards each. When you > copy a menu to a stack, you also have to place it on each card. Right now I > have a pre-placed menu on each card, and have duplicated the menu for each > stack, which I think is how it's often done. But I was hoping someone had a > better idea. Or I may have to use a floating menu stack after all.
Ok. What I did not seen was that a background object is only duplicate at the creation of a new card. Uhm ... I already imagine a client ask me to add an object into the background of a one hundred cards stack. Nightware! What I do not understand now it is you're need to duplicate the menu on each card. In a stack we can see only one card at the same time. Why do not just place the menu when you need it on the current card? I missed something here. I have to do some test to illuminate my mind. > What I've done is to have zero scripts in the menubar at all. It's just a > bunch of empty buttons. All the stacks are run by a > single backscript, and there is one menupick handler in there with all the > menu items in it (it's a pretty short menu.) That means > there is only one > handler to manage. > I thought about using behaviors, but I didn't see an advantage to it in this > situation. Would there be one? Behavior or other way to not have to repeat the same code. No particular advantage with it here. Just I had it in head when I wrote. ;) -- -Zryip TheSlug- wish you the best! 8) http://www.aslugontheroad.co.cc _______________________________________________ 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
