| Issue 2018: | Separate option for selection granularity from snapMinutes | |
| 3 people starred this issue and may be notified of changes. | Back to list |
Hi, I'm using fullcalendar with the grid set to 1/2 hour intervals (slotMinutes set to 30 minutes). I want the default click selection to be for a minimum of 1 hour events, but I want the start times to be in 30-minute increments. In other words, I don't want the user to be able to highlight any time slot that is less than an hour, but I want them to be able to highlight 1-hour slots beginning either on the hour or half-hour (i.e.: 1:30 - 2:30). If I set the snapMinutes to 60, this solves the first part by not letting them highlight anything less than 1 hour. However, it won't let the user select 1-hour slots that do not fall exactly within an even hour (i.e.: it will allow selection of 1:00-2:00 but not 1:30-2:30). I couldn't see a way to achieve this with the current fullCalendar implementation. I suggest an improvement that the snapMinutes option be separated out into two options: one option for which gridline the selection will snap to (snapMinutes), and another new option for selection granularity (selectionMinutes). This option would be the minimum number of minutes that the user could select, but it would be independent of snapMinutes. For my example above, I would then leave snapMinutes at the default of 30 minutes, and would set selectionMinutes to 60. It would also be great if this new option could then be updated dynamically (probably as part of https://code.google.com/p/fullcalendar/issues/detail?id=293) Here is a jsfiddle showing how the current implementation of snapMinutes only allows a minimum selection of 60 minutes but does not allow selection of time slots not beginning on the hour (ie: 1:30-2:30): http://jsfiddle.net/lcrees/9f82c/ Thanks!
Nov 2, 2014
Yes, I second this feature.
Aug 21, 2015
Discussion for this issue has moved to the following URL: https://github.com/fullcalendar/fullcalendar/issues/2283 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 |
Labels: Type-Feature