[alpha2] drop not firing when dragging between calendars
See original GitHub issueDrop not firing while draging event from one calendar to another. eventRecieve works while eventLeave doesnt exist in optionsInput. Docs say ‘When dropped, the eventLeave, drop, and eventReceive callbacks will fire.’
Feels like installation version of fc alpha2 over npm is not the same as these one’s here.
this is the config of both calendars
header: { left: '', center: '', right: '' }, editable: true, selectable: true, droppable: true, firstDay: 1, slotDuration: { minutes: 15 }, slotLabelInterval: { minutes: 15 }, slotLabelFormat: { hour: 'numeric', minute: '2-digit', omitZeroMinute: false, meridiem: 'short', hour12: false }, allDaySlot: false, columnHeaderFormat: { weekday: 'short', day: 'numeric', month: 'numeric' }, slotEventOverlap: true, displayEventEnd: false, defaultView: 'agendaDay', minTime: { hours: 6, minutes: 0 }, maxTime: { hours: 22, minutes: 0 }, dragScroll: true, nowIndicator: true, handleWindowResize: true, timeZone: 'local', navLinks: true, weekNumbers: true, height: 'auto', eventSources: [ this.eventList ], drop: (dropInfo) => { console.log('drop'); console.log(dropInfo); }, eventReceive: (info) => { this.calService.modifyActionPointDateOnDragDropWithDifferentOwner(info); }
Interesting enough, when external element is dropped to calendar , drop callback fires, but from calendar to calendar not.
Inspecting fullcalendar.d.ts for drop and eventReceive shows this below, while the arguments are totally different in the fullcalendar.js. eventLeave doesnt exist in fullcalendar.d.ts. I do have latest version of fullcalendar.d.ts
drop?(arg: { date: DateInput; allDay: boolean; jsEvent: MouseEvent; }): void; eventReceive?(event: EventApi): void;
Issue Analytics
- State:
- Created 5 years ago
- Comments:13 (5 by maintainers)
Top GitHub Comments
this has been addressed and released in 4.0.0-alpha.4
drop
now fires in this circumstancethe problem with
drop
not firing in this scenario has been fixed: fd3e878202668e5df6167c875897acbe89a04073 (in the v4 branch)I’ll comment on this issue again when released