[isDisabled]="disabled || isDisabled(node, nodeIndex(index))"
Because of the hardcoded disabled property, isDisabled cannot be reliably used to control which item is disabled.
Disabling the parent node automatically disables the entire tree under it and isDisabled is never called for those items.
It should behave like other functions - isChecked, isExpanded, isVisible etc - where you have full control over which item does what.
we request the feature, to have the possiblity, to create a new event, by doing a slot click + dragging the mouse + release to create a new event.
Can we expect this feature or do you can suggest a workaround using existing functionality to get a similar functionality?