Answered: As far as I can tell it behaves as specified. It might not be what you need, however. 1. It doesn't take the event end into account, i.e. it repeats the event based on its start, no matter when it ac...

Answered: Scheduling applications might get complex easily and I won't pretend DayPilot has a prebuilt solution for all the cases. One of the first things you may need to do is to switch from a simple one-tabl...

Answered: The recurrence is designed this way. The first event is always fixed and the following occurrences are generated using the rule. You can update the start date of this first event to match the rule (i...

Answered: You should move the first event so it matches the rule, please see also here: http://forums.daypilot.org/Topic.aspx/1376/reccurence-problem-in-week-view

Answered: The first event is not considered a part of the series. That's why it can have any start and it's not counted towards the limit when Times() rule is used. See also: http://forums.daypilot.org/Topic.a...

Answered: This is by design. The first event is always defined by its start and end. The subsequent occurrences are following the recurrence rule. This is how it works internally. However, you should be able t...

Answered: It's fixed now in the sandbox (build 6.4.2264). Thanks for reporting the issue!

Answered: There seems to be a bug in the code that expands the rule into the individual occurrences. I will need to fix the algorithm.

Answered: Recurrence is supported since 6.0 release: http://www.daypilot.org/daypilot-pro-6-0.html See also a tutorial for DayPilot Calendar: http://www.daypilot.org/calendar-tutorial-recurrent-events.html