When a plan have conflicting constraints on two activities (parent -10334 and child 289249), the scheduling conflict dialog appears, but does not trigger any of the change events when an option is applied.
I am using the advanced example, and added a change listener with a debugger to test.
transport: {
load: {
url: '../_datasets/testing.json'
}
},
listeners: {
change(e) {
debugger; // Does not hit debugger when scheduling conflict is resolved.
}
},
By default the initial round of calculations when loading a project is silent, to avoid excessive event triggering from normalizing large projects. This also silences conflict resolutions.