My favorites | Sign in
Project Home Issues
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 240: forceUpdate
5 people starred this issue and may be notified of changes. Back to list
Status:  Released
Owner:  ----
Closed:  Aug 2013


Sign in to add a comment
 
Reported by nicola.b...@gmail.com, Dec 10, 2009
Hi,
my propose is to introduce a "forceUpdateOnChange" in order to refetch
events at every change: viewChange and render.

Attach is fullcalendar.js modified, look at "BC" for changes.


fullcalendar.js
80.4 KB   View   Download
Dec 11, 2009
#1 koz...@gmail.com
How is this different than viewDisplay (Triggered once when the calendar loads and
every time the calendar’s view is changed. This includes when the prev or next button
is pressed) and adding a refetch events call to it?
Dec 11, 2009
#2 nicola.b...@gmail.com
viewDisplay is triggered AFTER the events are rendered, so it's necessary to remove
all events and rerender, but I've found a lot of difficult to resyncronize events.
I've used firebug to analyze network traffic and this method is the only one taht
sent only 1 request to json (events event) script.

Have you found other methods?

Thanks

Nicola

Dec 20, 2009
Project Member #3 adamrs...@gmail.com
 Issue 232  has been merged into this issue.
Dec 20, 2009
Project Member #4 adamrs...@gmail.com
kozefx, thanks for all your input on the issue. attaching a refetchEvents to the
viewDisplay was my first reaction too.

after thinking about it, if you attach a refetch to every viewDisplay, that might be
in addition to a refetch that it was already implicitly going to do, so sometimes you
will end up with 2 refetches.

the easiest solution is to have to a new option to force refetching. nicola, thanks
for the code. ill try to roll it into an upcoming release
Status: Accepted
Labels: -Type-Defect Type-Enhancement
Dec 21, 2009
Project Member #5 adamrs...@gmail.com
 Issue 253  has been merged into this issue.
Jan 14, 2010
#6 bibendus...@gmail.com
Need it soo much!!!
Did you add this option in the next release?
Feb 3, 2010
#7 katie.e....@gmail.com
Nicola, thanks for your code.  It definitely works.  Unfortunately with large amounts
of events it exasperates  Issue 178 .  Hopefully 1.4.4 comes out soon!
Feb 4, 2010
#8 bibendus...@gmail.com
I made a temporary fix for fullcalendar v1.4.4 to force events refetching while
changing view or day.

Take a look here:
https://code.google.com/p/fullcalendar/issues/detail?id=323&sort=-id&colspec=ID%20Type%20Status%20Milestone%20Summary%20Stars
Feb 5, 2010
#9 katie.e....@gmail.com
Nicola's patch incorporates very nicely into 1.4.4 - the code she put in 1.4.3 slides
into the exact same places.
Feb 5, 2010
Project Member #10 adamrs...@gmail.com
 Issue 317  has been merged into this issue.
Feb 5, 2010
Project Member #11 adamrs...@gmail.com
 Issue 323  has been merged into this issue.
Feb 6, 2010
Project Member #12 adamrs...@gmail.com
i was hoping to get this officially into 1.4.4, but ran out of time. this will be in 
the next release. thanks everyone
Feb 21, 2010
Project Member #13 adamrs...@gmail.com
ok, this is officially in 1.4.5 (just released). its called "lazyFetching"
http://arshaw.com/fullcalendar/docs/event_data/lazyFetching/

set it to false to make it refetch every time

thanks for the work and the suggestions!
Status: Fixed
Aug 13, 2013
Project Member #14 adamrs...@gmail.com
(No comment was entered for this change.)
Status: Implemented
Aug 13, 2013
Project Member #15 adamrs...@gmail.com
(No comment was entered for this change.)
Status: Released
Sign in to add a comment

Powered by Google Project Hosting