>How about having each member object initialized by themselves in INIT()?
Do you mean, to assign the properties? The thing is, if code somewhere changes the property at the container level, I want this change to cascade to the contained objects.
And for the initial value, I decided to "re-use" the assign method. I suppose I could have a separate method, which is called by the assign method, but I don't know whether this would give me any advantage.
>
>Just a thought...
>
>
>>Does the following make sense?
>>
>>I want to set key properties of a container at the container-level. The properties are really relevant for the contained objects, but I want to have key definitions in one central location.
>>
>>Assign-methods will copy the properties to the corresponding properties of the contained objects. In some cases, they will be copied as-is, in others, additional manipulation is required.
>>
>>Since I can give the properties at the container-level values in the property sheet, I force the assign methods to be executed, by assignments such as:
>>
>>
>>This.Property1 = This.Property1
>>
>>
>>Does this work, does it make sense, or is there perhaps a better way?
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
