On Thu, Sep 09, 2004 at 03:46:52PM +0200, Sylvain Wallez wrote: <snip/> > I started implementing an "on-create" event listener, but failed on that > same problem, as the whole form must be in a consistent state before > that event can be fired, because the event listener can potentially > reference any other widget.
What were you going to use "on-create" events for? I am guessing mainly for new repeater rows and newly referenced union cases? > So your initialize() stuff could be a solution to finish the > implementation of create-event. However, that event must also be fired > when a widget is creater later during the life for the form, e.g. when a > new repeater row is created. So initialize() must also be called in that > case. I already handle that case, and also calling initialize() for the created-on-demand child widgets of union widgets. Should I commit? --Tim Larson
