DayPilot.CellArray.invalidate

Hi Leo,

The purpose of the invalidate() method is to clear the cached cell customization results (the args.cell.properties values set in onBeforeCellRender). It doesn’t force a refresh of the cells. The cells are re-rendered when necessary, e.g. during an update() call, when events are moved (cells in the source and target rows), etc.

If you want to refresh all cells, calling update() is the best way.

Hi Dan,

Many thanks! I am fetching cell data async and then applying it, and looking to force a re-render of those cells that have new args.cell.properties. Is there a way to avoid updating all of them?

(We are fetching month by month async, meaning I usually only need to update one month albeit displaying multiple months.)

Thank you!

Do you fetch the cell data for additional months during scrolling?

No, no scrolling is involved. We allow switching between showing a month, 3 months and 6 months, as well as navigating back and forth a month.

So I just load whatever data was not fetched yet.

1. And what is the reason for not loading all the data at once? Does it take a long time to calculate it?

2. When you show 6 months, I assume that only a part of this time range is in the viewport. By default, the cells render progressively and onBeforeCellRender is only called for cells that are actually rendered. So if you load the data in advance (not necessarily at once), onBeforeCellRender will use it when first rendering the event.

1. Yes - it’s database/backend heavy. We use (some of) the cells to display utilization.

2. We enforce a minimum cell width, but adapt to screen size. Some of our customers have massive screens, so 3 to 6 months may actually fit on there (and they might want to see all the data at once…)

We can use the general update() method - I am just trying to optimise as much as possible and misunderstood the invalidate().