Overnight events aren't counted about google-calendar-hours HOT 5 CLOSED

Similarly: full-day events are not counted and that's a problem for me. I sometimes need to consider a full-day event as counting for 8 hours. It would be nice to provide a UI allowing the user to select one of two ways to handle full-day events:

1. Ignore
2. Consider each full-day event to be ______ hour(s)

from google-calendar-hours.

the problem is, there are multiple ways to solve this problem

a) count all event time in the day the event started
b) count all event time in the day the event ended
c) divide event time into portions so that time until 12am is recorded on day i, and time after 12am is recorded on day i+1

Each has their own merit for certain users
a) might be what most night owls would expect, but if you started work at 11:30pm and ended at 4am b) would make more logical sense
c) would be the most accurate depiction of what actually happened, especially if you had an event starting at 6pm on one day, and ended at 10am two days later, similar to defining a week start and end day, you could potentially allow users to specify roll over time of 3am or something.

c) is also the most challenging to implement since you theoreticaly have to handle cases where an event started in the distant past, and keeps going into the distant future. i'm not sure how the google api's allow for capturing time from such an event, if at all

the simplest solution might be allowing users to specify their own day end time and not worry about edge cases like multi-day events for now

from google-calendar-hours.

This needs to be sorted! Not sure if this project is dead. Someone needs to fork it and FIX this issue.

from google-calendar-hours.

would like to see dfsklar suggestion implemented

from google-calendar-hours.

Overnight events has been fixed with #138.

Note that full-day events are still not counted. This is by design.

from google-calendar-hours.