Our powerful JS Calendar component


Post by Animal »

It's not a delete event. That's why you are not getting these delete events.

This is all handled for you. Occurrences of recurring events are not real events stored in the store. They are ephemeral things which are only injected into the UI. I believe this is all explained in the docs.

Listen for the update event in the event store. The base event will have an update event fired from the store when it is updated: https://bryntum.com/products/scheduler/docs/api/Core/data/Store#event-update

It is simply updated to have an exception on that date.

Try this in the debugger command line when you are experimenting with your Calendar to find out what it can do, like we all do:

calendar.eventStore.on('update', function({ changes }) {
    if (changes.newExceptionDate) {
        console.dir(arguments[0])
    }
});

Post by Animal »

Here you can see the event log and I examine the record. After I have deleted the occurrence on the 13th and changed the occurrence on the 14th you can see that its exceptionDates property now has two dates.

Screenshot 2023-11-15 at 16.38.01.png
Screenshot 2023-11-15 at 16.38.01.png (269.17 KiB) Viewed 87 times

The "move" of the one on the 14th resulted in a new concrete event being added at that point. And you can process that as you normally process users adding events:

Screenshot 2023-11-15 at 16.42.15.png
Screenshot 2023-11-15 at 16.42.15.png (148.21 KiB) Viewed 87 times

Post Reply