My favorites | Sign in
Project Home Issues
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 1104: viewDisplay should always be called before eventRender
2 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 dan.mof...@gmail.com, Sep 6, 2011
viewDisplay gets called when the date range changes, but this gets fired last after all other events have fired.  This makes it significantly less useful for setting u data structures prior to other events.

Here's my situation.  I do some processing of the calendar to figure out which dates correspond with which table cells.  I only want to do this once every time the date range canges.  

In eventRender, i rely on this data to render my events.  I see no other way to reliably get called when the date range changes, but before eventRender.
Sep 6, 2011
#1 dan.mof...@gmail.com
Alternatively, you could make the loading event fire for more than just Ajax loads.  Make it fire before an event array is processed, or an event function is started.
Sep 6, 2011
#2 dan.mof...@gmail.com
Strangely, or maybe not so.. viewDisplay gets called first when using json.  Probably because the events are lazy loaded.  Perhaps if array events were likewise loaded lazily, then event firing order would not seem random.
Sep 29, 2011
Project Member #3 adamrs...@gmail.com
yeah, if there is ajax to fetch events, viewDisplay will get called before the eventRender's. if it is a normal array, other way around. i think it should be consistent. viewRender should always be called before. will make this change
Summary: viewDisplay should always be called before eventRender
Status: Accepted
Aug 13, 2013
Project Member #4 adamrs...@gmail.com
as of 1.6.3, viewRender (formerly viewDisplay) always gets called before events being rendered.
Status: Released
Labels: Type-BehaviorMod
Sign in to add a comment

Powered by Google Project Hosting