Jacque
I was hoping for a better answer from someone as well. I ended up doing what you did in a similar situation.

If its not too late, don't forget about the advantage of behaviors when adding all those menus. Maintaining one menuset and then parentscripting all the others has saved me lots of time when I need to change something in one of the menus.

Ron

On Jan 27, 2010, at 12:31 PM, J. Landman Gay wrote:

zryip theSlug wrote:

Here is what I could do to have this menu in each of my documents.
This is purely theoretical.
1) Creating of a substack in my project (as a kind of library) where I
could create the main menu
2) Creating a button with some script to handle my menu bar.
3) Creating a parentscript / behavior link between menu bar and its
code in the button
4) At every opening of a new document, copy of my group menu in the
new open stack. Provided of course that I have room in the top left
Maybe it can help, perhaps not. I tried ;)

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.

--
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

_______________________________________________
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

Reply via email to