Standalone won't run

[Peter Haworth]

That is an interesting idea.  I guess I'd be more inclined to update the
child controls by sending a message to their template that would update all
the controls of that tie, just becuase I think you'd probably want all the
controls of a specific type to look the same for HI purposes.  I guess you
could have a crop of each control that would cause it to be excluded from
the auto-update for exceptions.
Pete
lcSQL Software <http://www.lcsql.com>



On Tue, Jun 26, 2012 at 7:26 PM, Peter M. Brigham <pmbrig at gmail.com> wrote:

> The templatexxx (eg, the templatebutton, the templatefield) governs the
> properties of newly created controls only. Changing a property of the
> template<control> will not change anything in already-created controls.
> Nonetheless, setting the properties of the template<control> before
> creating a new control is a good way of generating a new control that looks
> and acts the way you need it to. You should remember to "reset" it when
> you're done.
>
> You could, I suppose, do something like what you're proposing by creating
> a template control with a customprop that is a list of long IDs and a
> mouseup handler that sets the properties of each of the listed controls to
> the properties of the template control. Then all you have to do is adjust
> your template's properties and click it, and... voila. Maybe require a
> control-shift-click to guard against accidental changes. Hmmmm...
> interesting idea. You could build in a way of storing the long IDs by
> script, maybe a repeat loop that waits for a mouseclick on a control then
> stores the long ID of the target, and exit the repeat loop by pressing the
> commandkey when you're done storing. Hey, this has possibilities!
>