v1.1.7

/

2018/09/23

Fixed:

  1. Fast typers who hit Enter on their keyboards to move to the next task line in Daycast may have ended up with text meant for their next task on the previous task’s line. We’ve corrected that. Daycast will now respond properly, getting the right text on the right lines.

Changed:

  1. To trigger the Task Reminders feature, users must specify their time of day preference with the ‘at’ symbol (e.g. @1pm).
  2. The ‘m’ in ‘am’ and ‘pm’ is now optional when using the Task Reminders feature.
  3. If using military time with the Task Reminders feature, Daycast will now recognize a variety of inputs. E.g., @0100, @100, and @1:00 all mean 1am.
  4. We’ve improved data syncing efficiency in a couple of ways with this release. Solo users and small teams are unlikely to notice much of a difference unless they re-install Daycast or install it on a new machine. Larger teams should experience noticeably increased syncing speeds.
  5. We’ve increased the frequency of our data integrity check for integrated time tracking services. When different systems exchange data, there are always opportunities for miscommunication: an internet connection somewhere on the journey from point A to point B that fails at the exact moment a piece of data makes the trip, for example, or unexpected errors that occur on either the sending or receiving end and disrupt the delivery of the data by stalling it, stopping it, or in some cases duplicating it. Part of Daycast’s service is checking to make sure that the data you send from your Daycast arrives at its destination accurate and intact. Prior to this release, our data integrity check ran once daily—leaving a window we decided was too wide. We now run our data check hourly for integrated time tracking services. Though we’ll never be able to eliminate the possibility of errors, we can catch and correct them sooner with this change.