4 Comments

You must be Logged on to comment or reply to a post.

  1. Andreas Kunz

    Good description of what’s happening!

    One detail which could also be mentioned to understand how UI5 rendering happens:

    In line 29707 you can see the “this.invalidate()” statement. This tells the UI5 core that there is a control, which has changed its state, so the visible rendering needs to be updated. UI5 will then wait with a zero timeout for any other such changes, and then triggering a rerendering. This means the renderers of all controls, which have been changed will be called and their updated HTML will be put into the DOM, so the user sees the new values.

    This invalidation can be suppressed by controls (hence the “if” around the statement, if for a certain property the DOM does not need to update of if the control wants to update the DOM directly without a complete rerendering of the entire control (this could improve performance for very large and complex controls, even though rendering is normally very fast).

    (0) 
    1. Jerry Wang Post author

      Hi Andreas,

      Thanks a lot for your comment. When I debug into the invalidate function as you mentioned, I have learned some new stuff. I have appended them into this blog. Thanks for your suggestion 🙂

      Best regards,

      Jerry

      (0) 

Leave a Reply