Page 1 of 1
[ANGULAR] Recurring Events Bug
Posted: Wed May 12, 2021 10:06 am
by ThomasH
Hey all,
Im currently working on a POC using the Bryntum Scheduler Pro Demo in Angular. One very important feature for us is the Recurring events feature. Following the docs and demo i found adding "enableRecurringEvents: true," in the top level config would sort me out, so I did.
I ended up with a weird bug I would like to check with the community, whether someone has experienced this before, or that I forgot an essential step in enabling recurring events. I could paste all the code here but I did not do much more than setting the enableRecurringEvents boolean to true and some small eventEdit customization.
Does this video suffice for some support? If not i can provide more information ofc!
Thanks in advance
Re: [ANGULAR] Recurring Events Bug
Posted: Wed May 12, 2021 1:18 pm
by saki
It is not yet supported in Scheduler Pro, the ticket is here: https://github.com/bryntum/support/issues/792
Re: [ANGULAR] Recurring Events Bug
Posted: Wed May 12, 2021 5:11 pm
by ThomasH
Thanks for the quick response! Does this mean i would currently need to use the non-pro Scheduler to achieve recurrence ? Cause I did see recurring events available in the Demos
Re: [ANGULAR] Recurring Events Bug
Posted: Wed May 12, 2021 5:20 pm
by saki
Do you mean this demo: https://bryntum.com/examples/examples-scheduler/recurrence/ ?
If so then it is actually standard scheduler included in Scheduler Pro examples browser. This is true for all examples that are in examples-scheduler
folder.
Re: [ANGULAR] Recurring Events Bug
Posted: Wed May 12, 2021 5:30 pm
by ThomasH
I was referring to that demo yes. Im currently using:
"@bryntum/schedulerpro-angular": "4.1.2",
"@bryntum/schedulerpro-trial": "4.1.2",
So if i understand you correctly I would need to use the normal scheduler component instead of the "<bryntum-scheduler-pro>" component to be able to use recurring events?
Re: [ANGULAR] Recurring Events Bug
Posted: Thu May 13, 2021 9:27 am
by saki
Yes, at the moment you should use the normal scheduler until the feature request is implemented: https://github.com/bryntum/support/issues/792#issuecomment-839607992
You can also decide to sponsor this feature to expedite its implementation