The scheduler in week-view and day-view is always starting at 12 am. We would like to request a simple function, which allows to let the calendar scroll to the desired hour! (Let's say it is 3PM and the user would see automatically see his appointments beyond 3PM, because that is what matters and not staring at 12AM ) Nobody want to look at a day view, which starts at 12am. There are in some forums suggestions mentioned how to potentially do it, but id does not work in all screen sizes without terribly breaking it! So please please add this small, but valuable feature...
Currently the scheduler 'snap' option does not actually snap to the nearest time slot, rather it adjusts the start time +/- the 'majorTick` amount of an event. So an event scheduled at 8:03 am would snap to 7:33 am or 8:33 am, given a 30 minute 'majorTick'. I would be helpful to have another option that allows the event to actually snap to the nearest time slot. So that same 8:03am would snap to 8:00am, 7:30am, or 8:30am.
Currently, if you create a recurring event, then edit a single occurrence (make an exception), and then later edit the series, the exception will be lost. Let's say you've booked a room from 10 - 12 every Tuesday for the next year, then edit a single occurrence maybe two months ahead, and then later need to perhaps correct a spelling error in the series title. The edit you made to the single occurrence would then be lost, and that's not so easily spotted... I would suggest letting the user decide whether or not to delete exceptions from the series when the series is edited.
Some schedules require appointments that exceed midnight (for discussion's sake, a company that operates night shifts to accommodate customers on the other side of the world). In this case I would like the "Monday" column to start at Monday 6pm to Tuesday 7am. This is instantly doable in WPF RadScheduleView by setting the property. I would expect this to be useful here as well, since there's an EndTime property it just needs to be expanded to display appointments correctly.
Having the ability to setup a recurrence outside of the scheduler would be nice. The ability to use recurrences for other things that don't make sense showing up on a scheduler. An example would be setting up a an email subscription. I want it to recur, but I don't need to see it on a calendar.
when the user edits a recurring appointment , a pop comes which ask the user to either edit a occurrence or series of that appointment. The content inside the appointment editor is based on which option is selected. Since the user can press (x) of occurrence or series popup. The event for cancel is becomes a necessity.Kindly provide cancel event of that popup.
When editing a recurring event it can occur than the POST call (the one that creates the exception) finishes well, but the PUT one fails. In this case the exception is created but the new event is not created, causing that the final user thinks that the event disappeared (and causing an inconsistency in database). It would be great if the scheduler could be configured to make one single call with the data of the master event and the new one in the same post, atomicly. Moreover, if it is needed to perform remote validation when resizing or moving one event of a serie (the same scenario as the previous one) it would be much more easier to do it with that single call model.
When setting the color for a Scheduler event resource, allow for a CSS class instead of a simple color.
We can get a string like FREQ=MONTHLY;INTERVAL=2;COUNT=2;BYMONTHDAY=19 but it would be great if there was an option to get a more readable format of the recurrence for labeling purposes (if you cannot already, I cannot find any documentation saying you can). Like, 'Recurring Every 2 months on the 19th, twice' or some such.
Currently, the moveEnd handler contains e.slot and e.resources objects to provide information about the slot where the event was dropped. Please add the corresponding fields to the moveStart handler to identify where the move began.
It will be fine to have a field "isReadOnly" on default scheduler datasource. This is to allow to share events like "public holidays", events of another users, ... or to prevent a user from changing an old event (according to business rules ...).
Currently we can edit recurrences for intervals equal or greater than a day but we can't create or edit an hourly recurrence. For example: I want to create a 30 min long event which gets repeated from 8:00 AM to 12:00 AM, every working day.
What about set the default start time for currentTimeMarker. Currently currentTimeMarker follows the browser time. This behaviour for each user login that has their own Time Localization. e.g. User A has Sydney time zone (UTC+10.00 Melbourne) then server will send the specific time to the Scheduler and currentTimeMarker will start based on that particular time. Event if User A look at scheduler in PC that use Kuala Lumpur time zone (UTC+08.00 Kuala Lumpur). Maybe add time Localization property for currentTimeMarker. But if it set null, it will follows current PC time.
Proposal: Add a property/function that specifies the resource group to take the task's background color from.
my dea is Timeline Month ,but no need to time phasing
To select multiple events from different groups in kendo ui scheduler with angular js, but currently it only allows multiple events selection in same group.
In date pickers in scheduler and occurence editor to easily be configured to show week numbers.
Scheduler events with long duration tries to refresh view area in IE and jumps to start position of event, However it works ok in chrome, it will be great if IE also behave smoothly as we see experience in Chrome. It will make dragging events by their last edge more smoothly.