| Issue 629: | Run selectHelper through eventRender/eventAfterRender callbacks | |
| 3 people starred this issue and may be notified of changes. | Back to list |
In the same way an event is dispatched when new events are displayed, an event should be dispatched before the 'selectHelper' is displayed so it can massaged. I've attached a patch which I'm currently using, and hopefully it will be generally useful. (ps: the new selection stuff is awesome — thanks a lot)
Aug 13, 2013
seems the best solution would be to run the event through the existing eventRender/eventAfterRender callbacks, probably passing in some special flag too.
Summary:
Run selectHelper through eventRender/eventAfterRender callbacks
(was: Callback when 'selectHelper' is rendered)
Labels: Type-BehaviorMod
Aug 14, 2013
(No comment was entered for this change.)
Labels:
-Type-BehaviorMod Type-Behavior
Aug 14, 2013
Can you give an example as to how that would be done? I am looking for a way to implement buttons in the selectHelper function, so the user can accept a booking directly in the selection. And thanks for sharing all that nice work!
Jul 22, 2014
(No comment was entered for this change.)
Labels:
milestone-skeleton
Jul 23, 2014
This is now the behavior in v2.1 (beta) http://blog.arshaw.com/1/post/2014/07/fullcalendar-210-beta.html I would really appreciate if you could verify this. Thanks a lot!
Aug 14, 2014
(No comment was entered for this change.)
Status:
Implemented
Aug 25, 2014
looks like eventAfterAllRender is called 2 times after eventDrop 2.1.0 beta3
Aug 25, 2014
really? i did a quick test and could not verify this. only called once in my case. is it something to do with your specific situation? can you whittle it down into a jsfiddle?
Aug 26, 2014
This issue has been resolved with the official release of v2.1.0: http://blog.arshaw.com/1/post/2014/08/fullcalendar-210-released.html Please post any follow-up bug reports or feature requests as separate issues. Thanks.
Status:
Released
|
|
| ► Sign in to add a comment |
Status: Accepted