ICEfaces
  1. ICEfaces
  2. ICE-9000

ace:dateTimeEntry - convert to use ice.ace.lazy

          Details

          • Type: Task Task
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 3.2
          • Fix Version/s: EE-3.3.0.GA, 4.0.BETA, 4.0
          • Component/s: ACE-Components
          • Labels:
            None
          • Environment:
            *
          • Assignee Priority:
            P2

            Description

            Convert component from current lazy initialization style to use new ice.ace.lazy.

            Tests had shown that current implementation registers ice.onElementUpdate for DateTimeEntry even when not yet initialized.

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              yip.ng added a comment - - edited

              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

              Show
              yip.ng added a comment - - edited 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
              Hide
              Permalink
              yip.ng added a comment - - edited

              ICE-9271, ICE-9291.

              Show
              yip.ng added a comment - - edited ICE-9271 , ICE-9291.

                People

                • Assignee:
                  yip.ng
                  Reporter:
                  Nils Lundquist
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: