altID

[Richard Gaskin]

David Bovill wrote:
>> By using properties to drive the control, the getProp and setProp
>> handlers just refer to "the target" to find the object being acted on,
>> so there's no need to hard-wire IDs anywhere in the scripts
>
> I've found that I've had to be very careful about using "the target" for
> groups that nest, and can share the same name> It only works in a general
> case when you use "the long id of the target"

Same here -- works a treat in every case I've needed it.

>> I'm sure there are cases where writing hard-wired IDs in scripts could
>> be useful, but I can't say I've ever needed to do so in my own work.
> 
>  Me neither - just trying to explore it - it would seem that if it is
> possible for a group to refer to its own controls using "btn id latID of me"
> syntax - this would be better than the alternatives as it would allow the
> end user to rename things?

If you're referring to sub-components within a group which is acting as 
a custom control, do you really want users to be able to rename those? 
If there's a need, would it make more sense to do so as a property 
setting of the containing group, where it could be managed?

As for the "custom control" group itself, yes, it should be renamable, 
and that should be easy to accommodate.

-- 
  Richard Gaskin
  Fourth World Media Corporation
  ___________________________________________________________
  Ambassador at FourthWorld.com       http://www.FourthWorld.com