We are use the Fullcalendar plugin for booking our events
Al lot of the events take place around midnight so often we see events starting at 22:00 and ending at 4:00. It is possible to insert these in Fullcalendar in the week view but it is a little tricky. It would make more sense to us to start the days at 8 in the morning and end at 8 in the morning so events will usually be visible in a single day.
I did not find this option in the documentation, so I would like to know if there is an existing implementation that does this job or else find a hint where I would start to enhance Fullcalendar to make this possible.
It is possible using the minTime and maxTime by setting them as the following.
minTime: "08:00:00",
maxTime: "32:00:00",
Here is a codepen showing this.
However it is quite buggy. If you try to put a small event into the time that would be the next day after 12PM, then the calendar does not really know what to do and the even will be be out of view. If the event is at least long enough to bring it to the next day past 8AM then it will be visible across both days. Due to the bugs with this method I would suggest using the calendar with its default minTime and maxTimes is the best approach.
Related
I have a rather strange problem. I'm trying to create URLs for Google Calendar items and everything is working fine, except when I add a timezone, the event start and end times are 5 minutes off. I can't for the life of me figure out what's wrong. Example:
http://www.google.com/calendar/event?action=TEMPLATE&text=Sample+Event&dates=20210511T1400/20210511T1500&ctz=America/New_York&location=&details=&sf=true
As you can you see from the URL, it should be 2PM and 3PM but when you actually go to the page, it's 5 minutes past the hour.
Anyone got any ideas?
Well finally found the answer. I was just missing the seconds from the time in the URL. That was messing it up. For example:
http://www.google.com/calendar/event?action=TEMPLATE&text=Sample+Event&dates=20210511T140000/20210511T150000&ctz=America/New_York&location=&details=&sf=true
Good afternoon,
I´m developing a calendar using FullCalendar scheduler and my client needs to see night shifts of a date that starts beyond 00:00 of the next day. I already know that nextDayThreshold allows to display events that occurs between two days establishing a time end limit but FullCalendar displays an event in the next day when it starts at 00:00.
One solution could be to create non standard Event fields like realStart and realEnd to store real dates and using start and event standard fields for visual representation but it has many unwanted effects. Ideas please?
I'm using the DatePicker for the first time and I noticed something which I find highly irregular, at least from my point of view. In my case the first day of the week is Sunday. Here is how the calendar looks for May 2016 on the DatePicker.
And here is an example of what I would like , as the Windows calendar.
If the first day of the week is a 1st I'd like to display the last week of the previous month not the other way around. Is there any way to customize this? I have looked over the documentation and other issues with customization but haven't been able to find an answer.
Can anyone tell me the best way of calculating the end date of a recurring event from the number of occurrences and the pattern in which the event occurs.
For example:
I have an event which has start date as 10/07/2014 (Tuesday) and occurs every week on Tuesday. This event will end after 10 occurrences (say). So, the my method should return me the end date as : 12/09/2014
The method should also consider more complex situations like suppose if the event occurs yearly on first Monday of October and has total 10 occurrences.
(This isn't an answer which gives you a complete solution by any means, but hopefully it's a step in the right direction.)
Good luck. I've worked on an ActiveSync implementation, and recurrent events are fundamentally painful. You'll need to think about all kinds of corner cases - if something occurs every month on the 30th, what happens in February? What happens if it happens at 1.30am, and the clocks go forward or backward in the event's time zone so that 1.30am happens 0 or 2 times for a particular day?
Noda Time can help with this, but it doesn't provide a complete solution, partly because all the requirements will vary so much.
The important types you'll need to know about are LocalDate and LocalDateTime to provide time-zone-neutral dates/times, and Period which represents a not-necessarily-fixed period of time, such as "1 month". That will help with things like "add a week" - and there are methods on LocalDate for things like "next Monday after this date". It gets harder for events which are "weekly, on Monday and Wednesday" - you'll want to step through the weeks, working out which days occur within a particular week, until you've gone through all the events you need.
Noda Time 2.0 has the concept of "adjusters" which will make life somewhat simpler for things like "the first Monday of October" but everything you need to do can be done with Noda Time 1.3. (Don't wait for Noda Time 2.0, which I wouldn't expect to be released for another 6 months at least.)
I think my strongest pieces of advice would be:
Keep it simple. Focus on getting the right results first, then work out any optimizations you need. (For example, don't try to "guess" when the 100th instance of an event will occur - stepping through 100 instances with simple steps will be slower, but get you to the right answer. Do measure the performance, but make sure you have good tests before you optimize.)
Introduce your own types to represent exactly what you know about the event. Use the Noda Time types where they match of course, but don't be tempted to use an existing type just because it's quite like what you're trying to represent. The small differences will bit you eventually.
Make sure you know what you actually want the results to be. Write lots of tests. Date and time work is a naturally data-oriented domain, so invest in making it as easy as possible to write tests for all the corner cases you should be thinking of. (And you really should be thinking about them. Pay particular attention to leap years and time zones.)
Be aware that time arithmetic doesn't follow the normal rules of arithmetic - x + 1 month + 1 month isn't the same as x + 2 months
If/when behaviour surprises you, do come back to ask specific questions here. There aren't very many of us working on Noda Time, but questions tend to be answered quickly :)
Has anyone using fullCalendar by Adam Shaw seen this before? The start time showing up in the calendar gets minutes added, however, when I click on the event and get the popup, I see the correct time.
For example, there are 3 events on different days and all of them have start time of 9:00a but when the calendar (weekly, daily or monthly) gets displayed, all times have 8 minutes added to them so it reads 9:08a
When I click on any of the events and I get the popup, the start time shows correctly 9:00a.
I have checked the database where these events are being read from and they are correct. Any help/suggestions will be greatly appreciated.
Thank you.