My favorites | Sign in
Project Home Issues
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 2416: Avoid rerendering after calling updateEvent
2 people starred this issue and may be notified of changes. Back to list
Status:  ExportedToGithub
Owner:  ----
Closed:  Aug 2015


Sign in to add a comment
 
Reported by sebricau...@gmail.com, Jan 12, 2015
Since rerendering is triggered after updating an event, it would be useful to have an 'updateEvents' function which updates a bunch of events before reporting them and triggering the redrawing.

This simple implementation works great for me:
https://github.com/BassT/fullcalendar/commit/7c14b02ab9bb9ddf24945a9f98c9f7e0a7372018
Feb 9, 2015
Project Member #1 adamrs...@gmail.com
The best solution API-wise is not completely clear to me, there might be a more generalizable solution, but yes I agree there should be a means to achieve this.

 Issue 2344  is related.
Summary: Avoid rerendering after calling updateEvent (was: Batch update events)
Status: Accepted
Labels: Type-Feature
Feb 10, 2015
#2 sebricau...@gmail.com
What do you mean by "more generalizable"?
Feb 10, 2015
Project Member #3 adamrs...@gmail.com
there are other methods that trigger rendering of events. maybe we can come up with a consistent API that prevents immediate rendering for all cases
Feb 10, 2015
#4 sebricau...@gmail.com
As far as I understand the working of the plugin, rendering of events is always triggered when the event data somehow changes. I think that's in general a good way to handle it, since it keeps the view consistent but as in this issue the performance of 'batch' operations can be improved by delaying the rendering.
Aug 21, 2015
Project Member #5 adamrs...@gmail.com
Discussion for this issue has moved to the following URL:
https://github.com/fullcalendar/fullcalendar/issues/2681

This is because Google Code is shutting down. Apologies if you are being pestered with these notifications. This is a one-time event.

Happy coding,
Adam
Status: ExportedToGithub
Sign in to add a comment

Powered by Google Project Hosting