So "any kind of data" (as in, "You can define custom properties for
any object, and use them to store any kind of data.") doesn't mean
"any kind of data," it means various "multimedia" kinds of data --
but not Rev objects?
Since the rest of the data I need to send to each instance of the
dialog will be stored in an array built from custom properties --
that seems to be the Rev-"native" way to do it -- it feels peculiar
to have to call up a different data stream for the operation. I
suppose I'm just being fussy.
I wonder if this limitation (if I understand it correctly) gets in
anyone else's way?
Charles
On Aug 1, 2005, at 12:06 PM, Ken Ray wrote:
On 8/1/05 7:44 AM, "Charles Hartman" <[EMAIL PROTECTED]>
wrote:
This has got to be simple, but I'm stuck: how do I get a group into a
custom property? I don't even need to do it from a script; the msg
box or Inspector will do.
The group includes an image and a bunch of little fields. I want them
in a cust prop because I'll have a lot of them and I want to automate
sending them to a dialog box.
How about just creating the group in an offscreen stack (or
substack) and
then doing "copy group <groupDesc> to <targetLoc>" every time you
want an
"instance" of the group?
Otherwise, you can't really store a true group object inside a custom
property AFAIK - you could store the binary of a stack with one
card that
only had your group on it, or you could store the specifications of
all the
objects that make up the group and then build it from scratch each
time
based on the specifications for each object.
But personally, I'd suggest the "copy group" approach...
_______________________________________________
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
