-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding all day events #13
Comments
I'm having the same problem and would love to see this option. |
All day events are not supported because we believe that all events should have the exact start time. To discussion. |
In the business world it is very common to have all day events. I enter all day events frequently in my Outlook calendar for work when it comes to things like trade shows, conferences, vacation days, etc. I would reconsider your position of all events having an exact start time because that is simply not always the case in typical business calendars and scheduling. |
Have recently started using atc and also came across the need to register an event for the entire day. It would be a good feuture to have since it allows devs to decide what the precise event data is instead of it being 'filtered' by your webservice. I do hope you reconsider and implement the change. :) P.s. thanks for the handy library+service! |
I love this script, but for my wedding I would love to make a all day event too on my webpage. This way there isn't any issues with people who get a personalized invite for only the party and not the ceremony or the dinner... |
Maybe I am missing this, but how do you add to calendar as an all day event? If i enter 00:00:00 or leave the time out completely it doesn't seem to function that way. Following the MSDN link below for outlook it appears to state "set the AllDayEvent property of the AppointmentItem object to true" when using C#. Not sure how this is handled on your side of things.
https://msdn.microsoft.com/en-us/library/office/ff184629.aspx
2016-05-04 00:00:00
2016-05-04 00:00:00
OR
2016-05-04
2016-05-04
The text was updated successfully, but these errors were encountered: