March 27, 2025, 11:33:28 PM

See more Support incidents in our old archived forum.

Author Topic: UseTimeRangeFilteredTasksInRows  (Read 1822 times)

tim

  • Customers
  • Jr. Member
  • *
  • Posts: 60
UseTimeRangeFilteredTasksInRows
« on: January 11, 2024, 12:15:21 PM »
We've enabled UseTimeRangeFilteredTasksInRows in our Application, which improved startup performance. Playing with the TimeRangeFilteredTasksTimeBuffer property we thought that increasing the buffer size would improve times needed for paging/scrolling from left to right. However the opposite is the case. The best startup and paging times are obtained when setting the buffer size to zero. Isn't it intended for that purpose? Where would you use it for otherwise?

Thanks!
Tim

ForumAdmin

  • Administrator
  • Jr. Member
  • *****
  • Posts: 96
Re: UseTimeRangeFilteredTasksInRows
« Reply #1 on: January 12, 2024, 04:47:59 PM »
Tim,

The Buffer is only useful when you want some task bars to "bleed" from just beyond the edges into the current time range. This would be useful if you have setup custom task templates that render tasks a bit outside of its time range - with some custom annotations, etc.

Now, if Buffer is set, then the Gantt would end up rendering more tasks than without and so entire load/page/scroll performance will go up.

And while paging/scrolling Gantt doesn't really reuse any of the already rendered tasks which is what you might have assumed (we understand, the property name might be a bit misleading, apologies for that).

Thanks
Praveen

tim

  • Customers
  • Jr. Member
  • *
  • Posts: 60
Re: UseTimeRangeFilteredTasksInRows
« Reply #2 on: January 15, 2024, 11:39:01 AM »
Thanks for taking the time for the detailed response. As we do not have something to display that requires "bleeding" we'll set the buffer size zero.

When paging/scrolling doesn't reuse any tasks to prevent rerendering them, what does?

I subscribed to the FilterTasksByTimeRange event and set the result as a LookupList as indicated in "...FlexyGantt/TimeRangeFilteredItems.cs#L114". Compared to not subscribing to the event at all and letting the library itself handle the filtering, this improved startup and paging/scrolling performace - but not enormously.

Tim