Our pure JavaScript Scheduler component


Post by saki »

Yes, I can reproduce the issue. Unfortunately, I do not have an immediate solution, only a clue that it is somehow connected with destroying the scheduler and then re-creating it again. I'll check the destroy process tomorrow.

Although create-destroy-create should work flawlessly, there is another approach demonstrated in our advanced example which uses reuse routing strategy. You can take a look at it meanwhile.


Post by saki »

I haven't found a workaround so I've created a ticket. You can follow it here: https://github.com/bryntum/support/issues/2663


Post by mils »

Thank you very much Saki.

Best regards


Post by jmeire »

Hi

I wondered if any workaround has been found yet in the meantime for the scheduler crash on 2nd create after destroy?

Kind regards
jmeire


Post by mats »

Not yet but we hope to have this ready in next release (few days away)


Post Reply