On Fri, 14 Dec 2001 19:50, Stefan Bodewig wrote: > On Fri, 14 Dec 2001, Jose Alberto Fernandez <[EMAIL PROTECTED]> > > wrote: > > I can't try it right now, but do you mean <script/> is broken too? > > > > :-) > > The example refers to a task by id and calls a method on it that > wouldn't exist in an UnknownElement.
anything that refers to another task or datatype is currently broken really badly if you expect it to behave the same as if it didn't have an id. > * Project keeps track of all tasks that have been created for a given > taskname. > > * If the definition of that taskname changes, tell all the tasks that > they are no longer valid > > * Make invalidated tasks replace themselves with UnknownElements, > which in turn would create the correct task instances when > maybeConfigure gets called. > > this is clumsy, I know. And likely to lead to more inconsistencies IMHO. -- Cheers, Pete ------------------------------------------------------- "When we remember we are all mad, the mysteries of life disappear and life stands explained." -Mark Twain ------------------------------------------------------- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
