All,
There's a bug I discovered (tested in IE 11, Chrome latest version) in Calendar Lite Version.
To reproduce the bug go here:
1)
http://www.daypilot.org/demo/Lite/Calendar/
2)
Pick an event to move (lets say pick event 7 on 8/3/2016). Before moving this event note mentally where the event starts (day: 8/3/2016, at 2 PM). Move that event somewhere else on the Calendar. Now try to move the same event back to its original location: (day: 8/3/2016, at 2 PM). You can't, the move is rejected,- at least its not rendered in the correct location. You can move the event anywhere else but the location where it first originated.
By doing further testing and looking at the posted data to the server during the callback event - move, it looks like the posted data is good and after rebinding the calendar and calling calendar.Update() on the server the rendered event on the client is still in the wrong place (only for the scenario described above). It looks like its purely client side issue, not server.
When trying the demo page of the Pro version this is not happening.
Is this going to be fixed in the Lite version?
Thanks,
Luke