| Issue 736: | Resize an event to a different day in agenda views | |
| 5 people starred this issue and may be notified of changes. | Back to list |
In week view I would like to be able to resize event to different day (e.g. Mon 16:00 - Tue 08:00).
Aug 13, 2013
(No comment was entered for this change.)
Summary:
Resize an event to a different day in agenda views
(was: resize an event to a different day in agenda views)
Labels: -Type-Enhancement Type-BehaviorMod
Aug 14, 2013
(No comment was entered for this change.)
Labels:
-Type-BehaviorMod Type-Feature
Aug 18, 2013
Issue 1458 has been merged into this issue.
Aug 18, 2013
Issue 1548 has been merged into this issue.
Jul 22, 2014
(No comment was entered for this change.)
Labels:
milestone-skeleton
Jul 23, 2014
This behavior is now possible 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!
Jul 23, 2014
Adam
We currently use the resize across days in the month view to actually
duplicate events as we don't allow multi day events so we capture the
resize event
and then capture how may days you have dragged across and create duplicates
of the original event with a different day but with the same times.
The resize across days feature does now work in the week agenda view ( not
quite as we wanted but we can handle that).
But now it seems it does not work in the month view which it currently does
with version 1.6.4
I used the same initialization code as below in versions 1.6.4, 2.0.2 and
2.1.0. I also used jquery-ui 1.11 and jquery 2.1.1
$('#calendarTest').fullCalendar({
header: {
left: 'prev,next today',
center: 'title',
right: 'month,agendaWeek,agendaDay'
},
firstDay: 0,
weekMode: 'fixed',
allDaySlot: true,
lazyFetching: true,
theme: true,
defaultEventMinutes: 60,
editable: true,
height: 500,
eventSources: [
{ url: '/get_sittings',
editable: true }
]
});
Jul 27, 2014
Your custom behavior (where resizing an event actually "clones" the event) seems a little weird to me from a UX perspective, so I'm a little hesitant to go through too much effort to accommodate it in the standard API, but if anything, there could be a simple boolean setting to disable multi-day resize. Gotta think about it. The resizing for *month view* events is probably a separate issue. Since 2.0, events *with times* that are in month view are not able to be resized with the mouse. Only timed events.
Jul 27, 2014
For us the agenda view resizing was a nice to have so we will not loose any sleep over whether it works or not but the event resizing in the month view is already in use so not having it will be a problem for us.
Jul 28, 2014
I took time-event resizing away in v2.0. The reason I did it was because it was unclear how the dates would exactly be manipulated after the drag. Let me pose a question to you. Say you have a single event that starts at 10:00am, and no specified end time. In month view, the user resizes it to one day longer. What do you expect the end date of the Event Object to become? What about the same scenario, but the event in question starts with an end time of 11:00am?
Jul 28, 2014
For both scenarios leave the times as they are but change the dates.
Jul 28, 2014
please elaborate. the subtleties of this issue are what I'm interested in. what would the `.end` value be in your mind after the resize? would it be the start of the next day? the end of the next day? the same time but on the next day? etc...
Jul 28, 2014
Firstly in my mind the concept of having an event without either a start or end time does make sense unless its an all day event. So the end value would be the new date with the same end time which is what happens now in version 1.6.4 on the month view when you drag across days. All we do is capture the fact that the event is resized across multiple days and deal with it accordingly. Unfortunately we are only putting a new front end on an existing system so we have to deal with some of the limitations we have which is events cannot span days but events can repeat over multiple days and have different start end times. As our events have a lot info attached our users like the concept of resizing across days to effectively duplicate the event and then editing the duplicates as required
Aug 14, 2014
(No comment was entered for this change.)
Status:
Implemented
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
Feb 26, 2015
What if i have an application using older version of the script and i cant upgrade to 2.0 atm? is there a trick for solving it on the older script version?
Feb 26, 2015
@julinotds, would be very hard to do w/o the 2.x code |
|
| ► Sign in to add a comment |
Status: Accepted