Included native support of every option update. See issue 293. #25

wants to merge 1 commit into


None yet
2 participants

An unelegant but working way to resolve "setters for all options" issue.
Some additionnal work could be done to upgrade performance, but in my case it is not an issue: I don't even see the latency. Maybe a note about the potential performance downgrade should be made in option() documentation.


arshaw commented Jul 27, 2013

I woud rather come up with a solution that doesn't destroy/rebuild the calendar every time. I wish there was some internal architecture where fullcalendar knew what to selectively re-render for any given option change. Hopefully we will get to this at some point. I'm still aware of the issue (it is immortalized in the Google Code issue tracker still), but I'll close this pull request, as it doesn't implement the solution optimally. In the meantime, users can call destroy/rerender themselves. thanks

@arshaw arshaw closed this Jul 27, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment