drop callback: getting the resource ID about fullcalendar-workspace HOT 10 CLOSED

eventDrop: function (event, delta, revertFunc, jsEvent, ui, view) {}

Also check your syntax on event.resourceId Note the lowercase 'd' (I was stuck on this!).

var blockedEvent = {
id: event.id+'booked',
title: '-unavailable-',
start: moment(event.start).subtract(30, 'minutes'),
end: moment(event.end).add(30, 'minutes'),
allDay: false,
resourceId: linkedRoomId,
backgroundColor: 'red',
editable: false,
anyOtherValue: 'myValue', //you can specify other objects too
//rendering: 'background' // BUG
};

to reference other values use blockedEvent.anyOtherValue

from fullcalendar-workspace.

@outofbounder thanks for the info.

Actually, my question is different. For external event dropping to the calendar, you have to use http://fullcalendar.io/docs/dropping/drop/ drop(callback) , not the eventDrop callback.

I had found my ways to do it; the drop callback has first parameter as date, but can be changed to dropLocation which will contains date, resourceId, allDay.

allDay also need to be hacked, to properly have a true or false value.

I didn't change the sourcecode coffee file, but change in the generated js files. (Otherwise, I will show my changes here.)

from fullcalendar-workspace.

No problem, I've been working around a few things myself. Have you tried something like this?
drop: function(date, jsEvent, ui, res) { // this function is called when something is dropped

then using res.id https://github.com/bkaluza/fullcalendar/blob/master/demos/external-dragging-resource.html

from fullcalendar-workspace.

nah. that repository is 3 years old. definitely not working with recent full-calendar.

from fullcalendar-workspace.

as per the docs

eventReceive: function (event, view) {
  var resourceId = event.resourceId;
  ...
}

from fullcalendar-workspace.

looks like the solution has been discovered

from fullcalendar-workspace.

@arshaw This is not closed. The eventReceive is a different callback. The drop callback is triggered when a valid jQuery UI object is dropped on the calendar/scheduler, NOT when an Event Object is dropped on the callendar. In the scheduler, the select callback has startDate, endDate, jsEvent, view, resource. The drop callback should have the resource too in he scheduler view, otherwise when I drop a jQuery UI object I cannot convert it into a valid fullcalendar Event Object.
In fact, because of the missing resource, I cannot tell where the element has been dropped

@dingzj How did you find the dropLocation callback? Doesn't seem to work for me.

from fullcalendar-workspace.

ah, now i understand. i assumed this was for eventReceive when it was actually an issue with drop.

from fullcalendar-workspace.

@50bbx

Here is my changes compare to the 2.4.0 version (of fullcalendar.js). The key part is last difference which use dropLocation, not dropLocation.start in the triggerExternalDrop function. Then the drop callback will be like drop : function dropEvent( dropLocation, jsEvent, ui, resource ) , you can easily get resource id by dropLocation.resourceId .

from fullcalendar-workspace.

this has been released in scheduler v1.2.0
http://fullcalendar.io/docs/dropping/drop/

from fullcalendar-workspace.