| Issue 2293: | no flicker on refretchEvents | |
| 4 people starred this issue and may be notified of changes. | Back to list |
Currently we have available only the refetchEvents, which destroys all the events and then trigger the ajax that catches all events and renders them all again. This is not the best way to implement an auto update, because the events are "flickering". The ideal would be to have an option that only UPDATE events. In other words, performs the Ajax and, according to the result, renders a new event that did not exist, update an event already rendered or removes an event that no longer exists.
Sep 25, 2014
#1
bhol...@snapappointments.com
Sep 25, 2014
Excellent suggestion. Would you mind providing the code for me to study it? Thank you so much!
Oct 30, 2014
(No comment was entered for this change.)
Summary:
no flicker on refretchEvents
(was: Make possible or implement an autoupdate)
Status: Accepted Labels: Type-Bug
Dec 15, 2014
Hi Adam, any news on this? I understand that this is a primary feature for a calendar. Unfortunately refetchEvents method is not good, because it destroy the events before firing the ajax request, so the calendar is empty for all the time you take the request. What can be long for slower connections.
Mar 12, 2015
Is there anything technically wrong with solving this by simply not doing destroyEvents() on the refetchEvents function? I just tried it and it seems to work well, updating the events without flickering. There must be some good reason behind destroyEvents() being there though, what am i missing?
Mar 18, 2015
I got the same issue with refetchevents. I need to refetch almost 150 events every 30 seconds. Calendars are shared on multiple computers and I cannot use socketIO/Node on this server. V1 refetched events very quickly. Why V2 so slow ?
Mar 25, 2015
If you comment out or remove the destroyEvents() function call inside refetchEvents() this actually fixes this problem, I played around a little bit with it and it did not seem to have any weird side-effects as far as I could see.
Aug 21, 2015
Discussion for this issue has moved to the following URL: https://github.com/fullcalendar/fullcalendar/issues/2558 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 |