I am having some issues with the time timeSelectionFeature. The first time the component loads, everything is working. If I close the component and reopen it, this.schedulerPro?.features is null. I get this error: "Trying to chain fn SchedulerPro#attachToProject, but plugin fn TimeSelection#attachToProject does not exist."
I'm not sure what I am doing wrong. This only seems to happen with the timeSelectionFeature. Other features like [resourceNonWorkingTimeFeature]="schedulerProConfig.features.resourceNonWorkingTime, will not throw any errors.
The problem still exists. For example, the first time I open the dialog box, Scheduler Pro displays and everything works correctly. If I close the dialog box and reopen it, I get the following error:
"Trying to chain fn SchedulerPro#attachToProject, but plugin fn TimeSelection#attachToProject does not exist."
This seems to occur only when the [timeSelectionFeature]="schedulerProConfig.timeSelectionFeature" property is set. If I remove it, opening and closing the dialog box works fine.
This also causes the this.schedulerPro.features to be undefined. I think there is something specific to the binding of [timeSelectionFeature] that is causing the problem. The rest of the properties seem to work fine.
I meant when opening it in a angular material dialog box . I click on a button > angular dialog box would open displaying the Scheduler Pro . First time it works correctly. Now when we close the dialog box and reopen it, that's when we get the error message regarding the timeSelectionFeature . It only occurs when I add this property.
When we do close the dialog box, I do call this.schedulerPro.destroy(); but it doesn't seem to be helping with the issue.
Thanks for sharing the details. As I can't reproduce with your test case inline-data updated.zip, could you please share a test case where we can reproduce this behavior with that Angular dialog box? So it will be easier for us to debug the issue on our side
That's a problem in that version 5.6.13, when I upgraded to 6.3.3, it's working fine. Please upgrade to the latest version (currently 6.3.3), and it should be working just fine!