I’ve finally reached the breaking point. The poor handling of repeating events in PostCalendar is getting an overhaul. I’m using the Palm Desktop calendar as my model for handling repeating events. This means the following cases will be handled once I’ve completed my development:
1) Edit the ‘current’ event a repeating event series
2) Edit all ‘future’ events in a repeating event series
3) Edit ‘all’ events in a repeating series (this is the current behavior of the software)
I’m building upon the PostCalendar code already embedded in OpenEMR. Since the PC code has already been modified beyond hopes of merging PC v5.0 (or higher) to work with OpenEMR I’m not worried about breaking some future upgrade path.
Once my development is finished and I’ve been able to successfully test it I’ll report back here to everyone so others can try it out.
The CVS codebase now has all the workings to handle repeating events much like Palm Desktop does. For those who’ve never use Palm Desktop let me clarify. There are three types of edits that can be made to a repeating event:
1) Edit a single day of a repeating event
—
This creates a new single-day event and modifies the original repeating event to exclude this single day.
2) Edit a single day and all future days of a repeating event
—
This creates a new repeating event starting on the single day. The original repeating event is modified to end on the day before the single day.
3) Edit all days of a repeating event
—
This is what the original functionality did. So nothing changed here.
The code changes not only affect edits to a repeating event but also DELETING a repeating event. For my purposes this closes a big hole in the functionality of the OpenEMR calendar. The code change will not affect past events nor does it need any database changes. I haven’t had a change to really work all the bugs out but it’s stable.