processEvents() should occur before msleep(), so that the Notify gets
displayed properly. msleep() before process events did not cause the
Notify to occur in opensuse Linux. Instead, an empty Notify appeared.
The Sessions graph on the overview page displays the start time of each session slice in a tooltip when the mouse is over the slice. Since this is displayed to the user, it should appear in the local time zone.
The daily screen displays day and time of the graph cursor as the mouse moves around the graphs. Since this time is displayed to the user, it should appear in the local time zone.
QT 5 changed the behavior of QDateTime::fromMSecsSinceEpoch to return the result in local time zone, whereas in QT 4, it returned UTC. On systems that do not support time zones, the QT 5 version still returns UTC. But for all other systems, the api change causes confusion in the SH UI because some date and time values are displayed in UTC instead of the local time zone. This manifests itself when the user is in USA which has a negative UTC offset. When selecting a date range to display in the overview screen, the displayed dates appear to be one day behind the selected date range.
For consistently, SH should always use UTC internally and only convert to the local time zone when displaying data to the user. This will ensure that the time zone information is preserved correctly when the UTC offset of the user's machine changes due to DST changes or traveling.
There are a few calls to fromMSecsSinceEpoch which should be using local time, and those will be updated in future commits.
QDateTime::fromMSecsSinceEpoch returns a QDateTime in the local time zone, but the ms input was created in UTC. This causes the day part to sometimes display off by a day on the graph x axis. This appears to be caused by a breaking change in QT 5. Previously, fromMSecsSinceEpoch returned a QDateTime in UTC, but in QT 5, it returns the date time in the local time zone.
