My favorites | Sign in
Project Home Issues
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 2471: snapDuration beginning at slotDuration's granularity
1 person starred this issue and may be notified of changes. Back to list
Status:  ExportedToGithub
Owner:  ----
Closed:  Aug 2015


Sign in to add a comment
 
Reported by f.albon...@gmail.com, Mar 26, 2015
Hi Adam and thanks for this great component.

I was playing around with slotDuration and snapDuration. What I would like to achieve is:
- a calendar with slots of 15 minutes (4 slots an hour)
- a selection that is at least 30 minutes, i.e. occupies two adiacent slots.

If i set FullCalendar up this way:
* slotDuration : '00:15:00',
* snapDuration : '00:30:00',
I am unable to select an event that starts let's say at 10:15 and ends on 10:45, as the snapping accepts only 10:00 or 10:30. Drag and drop also only accepts full or half hours. 

Is there a way around this limitation?

Fiddle here: http://jsfiddle.net/fabria/dmz1atsc/

Best regards
Mar 26, 2015
#1 f.albon...@gmail.com
Sorry, correct fiddle is http://jsfiddle.net/fabria/dmz1atsc/1/
Apr 19, 2015
Project Member #2 adamrs...@gmail.com
hmm, I see why you would need this, but I need to think about the best implementation. Currently not possible. Open to suggestions for the API
Summary: snapDuration beginning at slotDuration's granularity (was: slotDuration and snapDuration clarification)
Status: Discussing
Labels: Type-Feature
Aug 21, 2015
Project Member #3 adamrs...@gmail.com
Discussion for this issue has moved to the following URL:
https://github.com/fullcalendar/fullcalendar/issues/2736

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

Powered by Google Project Hosting