On Thursday 12 July 2007 23:51:27 you wrote: > isinited should be false initially. It is set right before calling > init and sending oninit, because it is used internally to prevent > init being called more than once. OK.
> Maybe a better thing would be to create your own flag to silence the > handlers and set that flag to true when you get the oninit event? That was my initial solution, however I found an instance where that doesn't work. If your views are being replicated, you have an initial instance before the data comes through (the data coming from the server, so well after the application has started). That instance has it's oninit method called, and then some time later the data is bound. Hmm, does ondata fire before or after the attributes are bound? If after, that would be the solution. (my wish is for finer-grained events for things like this. I'd love to have an event that says something like 'you are about to be deleted because your datapath node has gone', currently I'm manually doing that so I can register the deletion on the server). > Good advice for any project. The title of one of the chapters in > Fred Brooks's "Mythical Man Month" is "Plan to throw one away (you > will anyway)". I have yet to read that. I really should pick it up some time. -- Robin <[EMAIL PROTECTED]> JabberID: <[EMAIL PROTECTED]> Hostes alienigeni me abduxerunt. Qui annus est? PGP Key 0xA99CEB6D = 5957 6D23 8B16 EFAB FEF8 7175 14D3 6485 A99C EB6D
pgpvYdnwTgKFW.pgp
Description: PGP signature
