[Angular] taskRenderer is ignored when using virtualize

[methodeuser1]

Hi,

We're using taskRenderer to customize the content of individual tasks within the taskboard. However, we've noticed that when the virtualization option is enabled, the taskRenderer function is never called.

With virtualization disabled:

virtualize-off.png (29.15 KiB) Viewed 287 times

With virtualization enabled:

virtualize-on.png (6.81 KiB) Viewed 287 times

We've also implemented the getTaskHeight function but it's still not working

Since we have a large number of tasks in the taskboard, enabling virtualization is essential for performance reasons.

We'using Angular Taskboard component 6.1.5

Could you provide any suggestions or guidance on how to resolve this issue while keeping virtualization enabled?

Thanks in advance

[methodeuser1]

With virtualize option enabled we get this error on console:

virtualize-err.png (42.46 KiB) Viewed 283 times

[methodeuser1]

The error is always thrown by this snippet of code, because element for some columns is null

virtualize-debug.png (13.38 KiB) Viewed 283 times

[methodeuser1]

I think the cause of the problem is that the taskbaord component is reused between different routes (eg. boards/1, boards/2).
Is there a way to reset the taskboard component without recreate it ? (Maybe some init/reset function that we can insert inside ngOnChanges)

[marcio]

Hey methodeuser1,

Thanks for reaching out.

Could you please share a runnable test case for us? I tried on our demos and with virtualize enabled the taskRenderer function was called correctly.

[methodeuser1]

Sadly I don't have the effort to share a runnable example.
Nevermind, I think I've found the solution.

Just a question, how can I reset the taskboard component without the need to recreate it? Like an init()/reset() function tha I can put inside ngOnChanges()?

Thanks

[ghulam.ghous]

Hey there,

I believe we do not have any such api. We do have an api to destroy the calendar and then you can init another instance. But we usually recommend against destroying your components.

https://bryntum.com/products/taskboard/docs/api/TaskBoard/view/TaskBoardBase#function-destroy-static