Thanks to Ray for bringing this up
and thanks to Mark for his perfectly succulent getprops example...
6 years later, and now I get it! how getprops works...
who says you can't teach an old dog new tricks?
Hi Xavier,
Glad to see you are now taking a serious interest in getProp.
To answer the
Hi Ray
try this:
repeat with x = 1 to the number of controls in group G
put the long name of control x of group G cr after grpList
end repeat
make sure you refer to control x OF GROUP G or you'll get any control x of
the card you're in...
this is easily turning into an atomic function like
Hi Ray,
Use the following scripts as follows:
put the objects of grp 1
put the objectIDs of grp 1
Mind line wraps.
getProp objects
repeat with x = 1 to number of controls of the target
put the name of control x of the target return after myList
end repeat
sort myList
return
I forgot to add that you can put these scripts (see previous
e-mail) into the stack script or in a stack in use and they will
work for every object in the stack, including card and the stack
itself.
Best,
Mark
Mark Schonewille wrote:
Hi Ray,
Use the following scripts as follows:
put the
PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ray Horsley
Sent: Monday, 20 February, 2006 19:58
To: Discussions on Metacard
Subject: Re: What's in a group
Thanks to all. The only way I was able to come up with was
to ungroup the group, get a list of the selected objects, and
then group
Hi Scott,
There is hardly any difference. I suspect even that getprop
handlers and functions return their result in exactly the same
way.
The advantage of the property approach might be that you really
don't need to think about what the target may be. The function
needs a quoted string as
