| Issue 2479: | Where previously jqui `ui` object, better API | |
| 1 person starred this issue and may be notified of changes. | Back to list |
Hi,
I believe replacing UI object in some callbacks (like eventDragStart, eventDragStop or eventDrop) was completely misfortune as there is no easy reference to actual DOM object any more. Please, if possible bring back this functionality using:
this.view.trigger('eventDragStart', seg.el[0], seg.event, ev, seg.el);
this.view.trigger('eventDragStop', seg.el[0], seg.event, ev, seg.el);
this.trigger('eventDrop', el[0], event, dateDelta, undoFunc, ev, el);
where necessary!
For your info - it is hard to manipulate with extra classes applied to particular event DOM element directly.
Apr 19, 2015
I believe you can use `this` to grab onto the original clicked element, but I'm sure there is a way to get a reference to the "helper" (the cloned element actually moving). TODO: better document `this` add a way to get the currently moving element
Summary:
Where previously jqui `ui` object, better API
(was: Bring back UI object in callbacks instead of dummy)
Status: Accepted Labels: Type-Feature
Aug 21, 2015
Discussion for this issue has moved to the following URL: https://github.com/fullcalendar/fullcalendar/issues/2744 This is because Google Code is shutting down. Apologies if you are being pestered with these notifications. This is a one-time event. Happy coding, Adam
Status:
ExportedToGithub
|
|
| ► Sign in to add a comment |
I would even go to this code instead: this.view.trigger('eventDragStart', seg.el[0], seg.event, ev, seg); this.view.trigger('eventDragStop', seg.el[0], seg.event, ev, seg); this.trigger('eventDrop', el[0], event, dateDelta, undoFunc, ev, el); It's even better!