[REACT] Removing Event from EventStore triggers error

[tcs-rl]

Hi there,

We're using the Calendar in combination with the SchedulerPro.

While updating the Calendar and the SchedulerPro to 6.2.1 we ran into some issues while testing.

Last working version: 6.1.9

When we remove a event from the EventStore, while the event itself is selected, we're getting an error at:
"activeView.getDateFromElement is not a function" which was coming from "Calendar.onCalendarStoreChange"

While investigating this, we found that this line is causing the error:

const nextActiveDate = isScheduler ? activeView.getDateFromXY([activeItemPos.x, activeItemPos.y], null, false) : activeView.getDateFromElement(fallback),
            nextActiveEventId = fallback.dataset.eventId,
            nextActiveView = me.constructor.fromElement(fallback).closest(isCalendarMixin);

If you need more information, please let me know.

Best

[tasnim]

Hey,

How can we reproduce the behavior? Are you able to reproduce it with our online demo here https://bryntum.com/products/calendar/examples/calendar-scheduler/?

Could you please share the steps we can follow to reproduce the issue?

[tcs-rl]

Hey,

it seems I am unable to add "SchedulerPro" into this demo and I cannot find any example which does include it.
Ill try to get an example together.

Best

[Animal]

Yes, the isScheduler flag is not set there, and so it attempts to use the CalendarMixin API instead of the Scheduler API to ascertain the next active date.

https://github.com/bryntum/support/issues/11278

[tcs-rl]

Thank you, so I don't think an demo for this will be necessary.

Best

[Animal]

Hi there, we are examining how the Calendar accommodates a SchedulerPro instance as a mode, and we realized that the behaviour in this case is not well defined.

For example, the Calendar's event edit feature inherits from Scheduler, and is a simple editor. The SchedulerPro's event edit feature shows a much more featured editor.

I am thinking that given the use case, the SchedulerPro editor should always be used to edit events. (That would require that it had the allDay field added which would be shown only if there is an encapsulating Calendar instance)

[tcs-rl]

Hi,

as I understand this means there are some more potential issues with using the as mode right now?

In our case we don't use the Editor UI, since each of these are used across the entire application outside of the Calendar.

Do you need any more information about our use case for this?

Best

[alex.l]

Hi,

Thanks for providing this information.
Yes, there are some potential issues regarding that until the fix is merged.

No extra information required right now, our developers will contact if anything will be required. It will be very helpful if we'll stay tuned.