Does your eventStores have different dataset for these 2 schedulers, or you load same data for both but apply filter afterwards?
Hi Alex. Happy Monday. At the moment, each scheduler has a CrudManager that performs the exact same call to the backend. I then filter the top scheduler to resourceId=0 and the bottom scheduler to resourceId != 0. So I fetch the exact same data twice.
BUT.. This is only because I cannot run a single CrudManager to the schedulers so your highly reasonable question has two answers:
At the moment with two crudmanagers, I am loading the same data twice.
Once two crudmanagers are not need, I will only load the data once and filter in each scheduler to a disjoint set.
I can start tweaking the logic, sure, and build an extensive handler for dropping but if you will support a single crudmanger for two partnered schedulers soon, I would prefer to spend my dev time for something else?
Don't we have another thread regarding to this problem? As I remember there were 2 blockers: chained eventStore problem and chained resourceStore problem which are fixed now.
Here is an infinite loop
But this problem appears exactly because you copy-paste event with same id, because you have to use 2 crudManagers and have same dataset loaded in both schedulers, so when you drop, second scheduler already have exactly same event. So the problem in the solution.
The fix here should be to change approach and don't add/remove records, but only update assignment, so it will be filtered out in top scheduler and showed in bottom one. Or update the code and use one crudManager with chained stores, but you still will be need to change the approach and do re-assignment on drag/drop.
Thank you for the test case. I reproduced the problem, looks like it still doesn't work as expected. I've opened a ticket for that https://github.com/bryntum/support/issues/5977
We will try our best to find a solution for you as soon as it possible.
This is internally caused by the stores belonging to a project, when assigning an event store already part of a project to a Scheduler, that project is also assigned to the Scheduler - which in turn makes it use the resource store of the project. The tricky part in fixing is it that the event store can only be part of a single project. But we will figure something, your use case should be possible.
Meanwhile, I recommend also chaining the eventStore into the second scheduler. That way it should not pull the project over: