|
> I think I have some of this wrong Matt's description of these three events
is accurate. We moved "initialize" after child creation because most developers
were expecting the children to exist during this event. But that means
"initialize" is too late for setting properties which affect which
children get created. So we added "preinitialize" before
createChildren(). - Gordon From: Depending on what you want to do there may
be no discernable difference. Preinitialize comes very early in the
cycle, before any children are created I think. Initialize means the
children have been created but maybe aren’t laid out (measurement may not
be complete). creationComplete means it’s all done. I think I
have some of this wrong but that’s the basic idea. From: Can anyone explain a bit more about the preinitialize event? I've tried
to use it and is working the same as creationComplete (at least with the
Application tag). I've looked at the documentation but there's no information
available. YAHOO! GROUPS LINKS
|
