Each trip in the "Trips" tab gets an estimated trip duration from Google. This is stored as Est Hours and formatted as a time value (h:mm) for user readability purposes. This duration value is then used to produce suggested PU or DO times. However, switching RideSheet instance to another time zone can result in weird bugs where the suggested times are off by one or more hours. Best fix appears to be to change the formatting of Est Hours to a number so time zone has no bearing. 90 minutes would be stored at 1.5 rather than 1:30.
Each trip in the "Trips" tab gets an estimated trip duration from Google. This is stored as
Est Hoursand formatted as a time value (h:mm) for user readability purposes. This duration value is then used to produce suggested PU or DO times. However, switching RideSheet instance to another time zone can result in weird bugs where the suggested times are off by one or more hours. Best fix appears to be to change the formatting ofEst Hoursto a number so time zone has no bearing. 90 minutes would be stored at 1.5 rather than 1:30.