Sorry Mats, I did not read you reply as closely as I should.
Now realise that “childControlNames” is the documented version of
“controlNames” etc.
Thanks again
Terry
On 8 Mar 2014, at 13:08, Mats Wilstrand wrote:
> From 6.1 there are four new properties you can use for tasks like yours:
>
>
Hi Terry,
Check out Mats' e-mail. He has some good advice.
You can also set the behavior of a group to a button. That will solve
the script problem.
--
Best regards,
Mark Schonewille
Economy-x-Talk Consulting and Software Engineering
Homepage: http://economy-x-talk.com
Twitter: http://twitt
Thanks Mark,
The group is actually a group that contains the methods for drawing bar, line
and pie charts
and has 750 lines of script.
The objects I create in the group are lines, fields, rectangles etc. that are
created to make up the charts.
I currently have a property that contains a list o
Hi Terry!
>From 6.1 there are four new properties you can use for tasks like yours:
"controlIDs" reports the short IDs of all the controls of a card or group.
(undocumented)
"controlNames" reports the short names of all the controls of a card or
group. (undocumented)
"childControlIDs" reports the
Hi Terry,
Why don't you simply delete the group and create a new one?
If you want to have a list of controls of a group, card or stack, you
can use a repeat loop in a getProp handler:
getProp allControls
repeat with x = 1 to the number of controls of the target
put the long id of contro
