Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

  • stonebranch2
    replied
    Thank you

    Leave a comment:


  • Isomorphic
    replied
    recordComponentPoolingMode only affects recordComponents that you create via the createRecordComponent() API.

    Leave a comment:


  • stonebranch2
    replied
    Thank you for the quick feedback.

    Does the poolingMode "recycle" have an impact on anything else, or does it only apply to the components we create/update from createRecordComponent/updateRecordComponent.

    Regards
    Last edited by stonebranch2; 20 Jul 2022, 12:03.

    Leave a comment:


  • Isomorphic
    replied
    The most efficient approach would be to just output some HTML for a scaled image from a CellFormatter, which is really pretty simple (<img width=value/field.width height=cellHeight ...).

    If you with recordComponents for this, remember to set poolingMode to "recycle" (which is what causes updateRecordComponent to be called).

    You are correct that there will be negligible performance cost if the field is hidden.

    Leave a comment:


  • stonebranch2
    started a topic Progressbar ListGrid Questions

    Progressbar ListGrid Questions

    Hi Isomorphic,

    Just want to confirm the best way to add a progress bar (Progressbar) to a ListGrid is still by setting both of the following,

    Code:
    setShowRecordComponents(true);
    setShowRecordComponentsByCell(true);
    and implementing the methods to create/update the Progressbar component.

    Code:
    createRecordComponent
    updateRecordComponent
    Also, can you confirm that if the Progressbar field is hidden, there will be no extra performance cost even though setShowRecordComponents and setShowRecordComponentsByCell are enabled on the ListGrid? I want to make sure that we only incur an additional performance cost if the user chooses to add that field to the Visible Fields.

    Thank you
Working...
X