Done exactly same as checkboxbutton (and linkButton and pushbutton.) But this was actually not the cause of "registers ice.onElementUpdate ... even when not yet initialized." There was already a form of lazy init. since "rev. 31899 01/11/12 10:43 AM."
The cause was actually a side effect of the lazy init. setup for popup calendar. The onElementUpdate in question was used to clean up lazy init. setup objects. It was registered right after lazy init. setup mostly likely to utilize closure access to the objects. A separate onElementUpdate was registered right after lazy init. construction.
Changed to merge the two into one and done after lazy init. construction. This also solved the issue raised by Mark about "double registration for same id."
M: C:\svn\ossrepo\icefaces3\trunk\icefaces\ace\component\resources\icefaces.ace\datetimeentry\datetimeentry.js#34899
Task
Major
MODIFY
/icefaces3/trunk/icefaces/ace/component/resources/icefaces.ace/datetimeentry/datetimeentry.js
Done exactly same as checkboxbutton (and linkButton and pushbutton.) But this was actually not the cause of "registers ice.onElementUpdate ... even when not yet initialized." There was already a form of lazy init. since "rev. 31899 01/11/12 10:43 AM."
The cause was actually a side effect of the lazy init. setup for popup calendar. The onElementUpdate in question was used to clean up lazy init. setup objects. It was registered right after lazy init. setup mostly likely to utilize closure access to the objects. A separate onElementUpdate was registered right after lazy init. construction.
Changed to merge the two into one and done after lazy init. construction. This also solved the issue raised by Mark about "double registration for same id."
M: C:\svn\ossrepo\icefaces3\trunk\icefaces\ace\component\resources\icefaces.ace\datetimeentry\datetimeentry.js#34899