Our pure JavaScript Scheduler component


Post by markusmo »

Hi
We had a look at https://www.bryntum.com/examples/scheduler/multiassign/ and are thinking to implement this into our application.
During review of this implementation, we came across following questions:
We assign the same task to two resources, one resource is not in the viewport, so we do not see it.
How do we know, that this assignment does not result in a conflict of tasks?
While rescheduling this event, how do we know, that there is not conflict of tasks?

Is there a best practice implementation to handle such cases?

Post by Maxim Gorkovsky »

Hi.
How do we know, that this assignment does not result in a conflict of tasks?
What do you mean by conflict? tasks overlapping on same resource? If so you can listen to beforeEventDropFinalize event, check if new task date doesn't conflict with any existing task and if it doesn - return false preventing drop.

Post by markusmo »

Hi
Thanks for the hint.

Will this event be triggered for all resources once or only once per scheduler?

Post by Maxim Gorkovsky »

Event is fired once after event is dropped, context contains all required information

Post by markusmo »

How would you visualize this collision?
Is there a best practice?

Post by Maxim Gorkovsky »

When we face a constraint-related collision in ExtGantt we show a popup with message for user. You can do same with openPopup method for example.

Post Reply