>3) when you create a new object, it is a perfect copy of the template >; some of >its properties are set (the id, the layer ...) all other properties >are empty ie >inherited from the the template. >If you edit some property of the object (for example move it), the >property has >a value and is no longer inherited from the template. >Metacard works already like that with colors and fonts... > I agree it should work this way, but I don't like the idea of having to set aside a separate stack to use as the templatestack. It should work like images and buttons. An image can be in any stack and can be displayed through ab button by setting it's icon property to an image id. If you set an icon of a button, then delete an image I believe the button's icon goes blank. Same thing should happen with templateobjects or... create a new object called a viewer. This viewer would display any object like: set the viewercontrol of viewer 1 to btn 1 of cd 2 of stack "dummy" set the viewercontrol of viewer 2 to group 1 of cd 1 of stack "dummy2" Any of the viewer's properties would be inherited from the viewercontrol until changed. You delete the viewercontrol the object simply goes blank. In addition, there should be a property called sharedcontrol which would work like sharedtext in groups, where changing a property of a viewer would change the viewcontrol's property (which changes the properties of all it's children for which that property was not explicitly set). If you wish for a viewer to inherit a certain property again, set that property to empty. I think I've done enough damage now... regards, Tuviah Snyder Diskotek Custom Application Development & SuperCard/HyperCard Conversion at a low price
