| Issue 656: | Blocking/constraining events to "Background" events | |
| 15 people starred this issue and may be notified of changes. | Back to list |
Hi i want to know how to block slots in the full calanedar and prevent those slots being selected Thanks
Oct 7, 2010
Project Member
#1
adamrs...@gmail.com
Status:
Discussing
Oct 7, 2010
Hi adamrshaw .. actually i am making use of full calendar for an appointment management system . In the full calendar agenda day view we have the slots for complete 24hrs which are all enabled for use . What i want is to enable only the business hour slots for ex: say( 9am-6pm) and disabling "dayClick" for the rest.
Jan 1, 2011
ok i understand. i'd imagine this being related to issue 496 , but we'll see how it pans out
Status:
Maybe
Sep 29, 2011
Issue 1093 has been merged into this issue.
Sep 29, 2011
this issue will be about rejecting dragging + dropping events into these areas. issue 496 will be about just the superficial rendering aspect. but issue 496 would need to implemented first
Oct 2, 2011
(No comment was entered for this change.)
Summary:
blocking of slots (for "Background" events)
Oct 2, 2011
Issue 1114 has been merged into this issue.
Sep 27, 2012
Hey Adam! Have there been any developments in this area so far?
Aug 13, 2013
(No comment was entered for this change.)
Summary:
Blocking of slots for "Background" events
(was: blocking of slots (for "Background" events))
Status: Discussing Labels: Type-Feature Blockedon: fullcalendar:496
Aug 15, 2013
Issue 1344 has been merged into this issue.
Aug 15, 2013
(No comment was entered for this change.)
Summary:
Blocking/constraining events to "Background" events
(was: Blocking of slots for "Background" events)
Aug 18, 2013
Issue 1529 has been merged into this issue.
Aug 18, 2013
Issue 1564 has been merged into this issue.
Jun 7, 2014
Issue 2135 has been merged into this issue.
Jun 7, 2014
Issue 2135 brings up the issue of preventing these dates from being selected, and preventing events from being dropped in them.
Sep 2, 2014
merging this with the more general issue on prevent certain events from overlapping, which should be robust enough to handle "background" events specifically as well.
Status:
Duplicate
Mergedinto: 396 |
|
| ► Sign in to add a comment |