I'm not sure I'm getting the bigger context here... I think you're
looking for a way to allow others to author your menus, is that correct?
If so, I'd suggest taking the menus' content out of Director, and use
an xml import to populate the menus. Write a recursive menu builder
which parses the xml and builds you base menu, and stores the info
for the submenus. Then anyone can modify the xml and never has to see
Director. Another advantage is that you can use that menu data in
another app, like Flash, if you need/want to switch techs down the line.
2 cents,
Kurt
Hi All,
I'm trying to create a behavior that allows the user to select a field
member from a dropdownlist. This member contains a property list
that would
be used to generate a dropdown menu for the next selection in the
getPropertyDescriptionList dialog box. (this is for use at
authoring time
only)
I was trying to find a way to do a callback from the gdpl and came
across
the runPropertyDialog function. My thinking is that I would have the
runPropertyDialog function fire off a mui dialog box to select the
field
member then return that info to the gdpl so it can pull the value
of the
field and present a dropdownlist.
Does this make sense? Am I totally misunderstanding what can be
done with
this? Any suggestions on how to build the mui dialog box to select
the field
member, if I'm on the right track.
Thanks in advance.
Daniel
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/lingo-l.cgi To post messages to the list, email
[email protected] (Problems, email [EMAIL PROTECTED]). Lingo-L is for
learning and helping with programming Lingo. Thanks!]
