When using the datetime control, the hour element doesn't default to the current time. The value seems to be one hour behind - I have seen a previous post relating to UTC time post back in Jan 2011, not sure if this has been fixed, if so could this be linked to British Summer Time / GMT? Is there a mechanism to work around this problem.
Thanks
Damian,
Sounds like a bug. It's been filed at
https://code.google.com/p/opendatakit/issues/detail?id=961. Since it's
likely device and timezone specific, it'd be great if you could add
that information to the ticket.
As far as a workaround, first, make sure your device time is actually
correct. Then try using the time only widget
(http://opendatakit.org/help/form-design/examples/#date_prompts) or
have the user enter the hour in an integer widget with a 0-24 hour
constraint.
Yaw
On Mon, Jan 13, 2014 at 1:25 AM, DamianLindley@aol.com wrote:
When using the datetime control, the hour element doesn't default to the current time. The value seems to be one hour behind - I have seen a previous post relating to UTC time post back in Jan 2011, not sure if this has been fixed, if so could this be linked to British Summer Time / GMT? Is there a mechanism to work around this problem.
Thanks
--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en
You received this message because you are subscribed to the Google Groups "ODK Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to opendatakit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.