You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I thought we could do that, but that definitely caused crash. Unfortunately I don't have time to reproduce to show an example. Just wanted to report it.
A hacky solution that I had to do to get desired behaviour was to:
thanks. there have been other reports that are somewhat related. the crux of the problem is that a view rerender is being called from within a viewRender callback, causing infinite recursion. there should be a safeguard against this.
arshaw
changed the title
Crash while setting option
Infinitely recursive view rerender, crash
Feb 10, 2017
Here's the root of the problem: a dynamic options change almost always results in a full view rerender, which calls the viewRender callback, which results in infinite recursion.
One potential solution: if the option being changed is already set to the given value, do nothing. This approach would prevent infinite rerenders. It would only result in 2 renders.
Another solution is to ignore rerenders that are initiated in the viewRender callback. Though I fear some people would want the ability to initiate a rerender, and this would constrain them.
FYI, the rerender does queue up until after the viewRender is executed, but still a type of recursion nonetheless.
I was trying to prevent editing in month view and allow it only in agendaDay view.
I tried this:
I thought we could do that, but that definitely caused crash. Unfortunately I don't have time to reproduce to show an example. Just wanted to report it.
A hacky solution that I had to do to get desired behaviour was to:
just in case someone needs
The text was updated successfully, but these errors were encountered: