| Issue 1647: | Call to 'rerenderEvents' does not work if fullCalendar div has been resized horizontally (agendaDayView). | |
| 1 person starred this issue and may be notified of changes. | Back to list |
My application manually handles height and width of calendars and allows for resizing the multiple calendars being displayed to fit to screen or to an integer pixel width specified by the user. The event 'rerenderEvents' would seem to be appropriate since no reload is required, simply a redraw.
Steps:
-programmatically change the width of the fullCalendar div.
-call 'rerenderEvents' on that fullCalendar
What you expect: all the events to rerender with the same amount of blank space available.
What you see: events are rerendered, but their width is not changed, so if the new width is smaller than before, the little section to the right of empty space is lost. If the new width is larger, there is excess empty space.
Fix: I noticed that 'render' works, and it seems that's because the logic flow eventually hits function updateSize--which is VERY similar to the code from function rerenderEvents, only with a little bit more. So I added the calls to markSizesDiry, calcSize(), setSize(), and unselect() that are present in updateSize before the actual clearing and rendering of events. New function looks like this:
// attempts to rerenderEvents
function rerenderEvents(modifiedEventID) {
markEventsDirty();
++ markSizesDirty();
if (elementVisible()) {
++ calcSize();
++ setSize();
++ unselect();
currentView.clearEvents();
currentView.renderEvents(events, modifiedEventID);
currentView.eventsDirty = false;
}
}
And this works just fine for me, much faster than a new call to 'render'.
***Note that this may not apply to agendaWeekView, I do not currently use that.
Aug 21, 2013
Project Member
#1
adamrs...@gmail.com
Status:
ReproTemp
Aug 25, 2013
This message is being bulk-sent to a number of issues, both [very] old and new.
I have been working on taming this issue tracker, which has gotten out of control after months of neglect. You are receiving this message because I could not successfully reproduce the bug you were reporting with a reasonable amount of effort. I have written some new bug-report guidelines to be used by all bug reports going forward:
http://arshaw.com/fullcalendar/wiki/Report-a-Bug/
Its salient point is that all bug reports should have an isolated demonstration, viewable online with a tool like JSFiddle.
If the bug you originally reported is still important to you, could you please first try the latest version of FullCalendar and see if it is fixed? If not, could you please file a NEW bug report that follows the new guidelines? This issue will not be monitored for further comments.
I'm sorry I have taken so long to respond to many of your request, and I'm sorry if this new procedure causes extra work for you. Going forward, the issue tracker will be much more of a well-oiled machine.
Again, if you must, PLEASE SUBMIT A *NEW* BUG REPORT (following the new guidelines) INSTEAD OF COMMENTING ON THIS ONE. Further comments on this report will be ignored. Thanks.
Status:
Invalid
Labels: Type-Bug |
|
| ► Sign in to add a comment |