Time field with possible bug

Development
1

Hi everybody,
we think we have a bug in the time field:
the GMT value is lost when

To replicate the bug you can load the attached form and behave as follow:

  1. reach the time field and put an hour you want (or the one it preloads).
    If you check the instance output XML we can see the correct hour + the GMT
    value, in our case GMT +2.
  2. Press the back button, save the form, than, from the main app menu,
    reload the form you were filling, go to the hour field: YOU CAN SEE THE
    FIELD CHANGED HIS VALUE TO AN HOUR LESS THAN THE PREVIOUS VALUE, and if you
    continue to do the same thing (exiting and entering the form) you'll loose
    an hour every time.

Could be a bug? Or we're missing something?

We tried the last odk collect app and the problem is still there.

Thank you very much
Angelo

timebug.xml (1.09 KB)

2

Hi all,
sorry, there is a wrong step in my explication: you firstly have to save
and than check the instance file. Sorry.

Thank you very much
Angelo

··· El jue., 14 may. 2015 a las 12:05, Angelo Lazzari () escribió:

Hi everybody,
we think we have a bug in the time field:
the GMT value is lost when

To replicate the bug you can load the attached form and behave as follow:

  1. reach the time field and put an hour you want (or the one it preloads).
    If you check the instance output XML we can see the correct hour + the GMT
    value, in our case GMT +2.
  2. Press the back button, save the form, than, from the main app menu,
    reload the form you were filling, go to the hour field: YOU CAN SEE THE
    FIELD CHANGED HIS VALUE TO AN HOUR LESS THAN THE PREVIOUS VALUE, and if you
    continue to do the same thing (exiting and entering the form) you'll loose
    an hour every time.

Could be a bug? Or we're missing something?

We tried the last odk collect app and the problem is still there.

Thank you very much
Angelo

--
You received this message because you are subscribed to the Google Groups
"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

3

I believe you are experiencing this issue:

https://code.google.com/p/opendatakit/issues/detail?id=1075
https://groups.google.com/forum/#!searchin/opendatakit-developers/1075/opendatakit-developers/Ds82cwZNwbo/pnqA9Azxux8J

I have plans to fix this but I'm not sure when I'll get time.

··· On 14 May 2015 at 06:10, Angelo Lazzari wrote:

Hi all,
sorry, there is a wrong step in my explication: you firstly have to save
and than check the instance file. Sorry.

Thank you very much
Angelo

El jue., 14 may. 2015 a las 12:05, Angelo Lazzari (< lazzari.angelo@gmail.com>) escribió:

Hi everybody,
we think we have a bug in the time field:
the GMT value is lost when

To replicate the bug you can load the attached form and behave as follow:

  1. reach the time field and put an hour you want (or the one it
    preloads). If you check the instance output XML we can see the correct hour
  • the GMT value, in our case GMT +2.
  1. Press the back button, save the form, than, from the main app menu,
    reload the form you were filling, go to the hour field: YOU CAN SEE THE
    FIELD CHANGED HIS VALUE TO AN HOUR LESS THAN THE PREVIOUS VALUE, and if you
    continue to do the same thing (exiting and entering the form) you'll loose
    an hour every time.

Could be a bug? Or we're missing something?

We tried the last odk collect app and the problem is still there.

Thank you very much
Angelo

--
You received this message because you are subscribed to the Google Groups
"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups
"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Tom Smyth

Worker-Owner, Sassafras Tech Collective
Specializing in innovative, usable tech for social change
sassafras.coop · @sassafrastech

Resident, Touchstone Cohousing
touchstonecohousing.org

4

Hi,
we need to get this issue solved but knowing is not a high priority bug for
the comunity, we're triyng to solve it by ourselves but we blocked in the
code because we cannot find where the ODK reads from the XML the value, so
we cannot debug correcly the issue.

So, can you kindly tell us where is the point where the app reads a value
and than we will be able to focus on it our debug?

THANK YOU VERY MUCH!
Angelo

··· El jue., 14 may. 2015 a las 15:14, Tom Smyth () escribió:

I believe you are experiencing this issue:

https://code.google.com/p/opendatakit/issues/detail?id=1075

https://groups.google.com/forum/#!searchin/opendatakit-developers/1075/opendatakit-developers/Ds82cwZNwbo/pnqA9Azxux8J

I have plans to fix this but I'm not sure when I'll get time.

On 14 May 2015 at 06:10, Angelo Lazzari lazzari.angelo@gmail.com wrote:

Hi all,
sorry, there is a wrong step in my explication: you firstly have to save
and than check the instance file. Sorry.

Thank you very much
Angelo

El jue., 14 may. 2015 a las 12:05, Angelo Lazzari (< lazzari.angelo@gmail.com>) escribió:

Hi everybody,
we think we have a bug in the time field:
the GMT value is lost when

To replicate the bug you can load the attached form and behave as follow:

  1. reach the time field and put an hour you want (or the one it
    preloads). If you check the instance output XML we can see the correct hour
  • the GMT value, in our case GMT +2.
  1. Press the back button, save the form, than, from the main app menu,
    reload the form you were filling, go to the hour field: YOU CAN SEE THE
    FIELD CHANGED HIS VALUE TO AN HOUR LESS THAN THE PREVIOUS VALUE, and if you
    continue to do the same thing (exiting and entering the form) you'll loose
    an hour every time.

Could be a bug? Or we're missing something?

We tried the last odk collect app and the problem is still there.

Thank you very much
Angelo

--
You received this message because you are subscribed to the Google
Groups "ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups
"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Tom Smyth

Worker-Owner, Sassafras Tech Collective
Specializing in innovative, usable tech for social change
sassafras.coop · @sassafrastech

Resident, Touchstone Cohousing
touchstonecohousing.org

--
You received this message because you are subscribed to the Google Groups
"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

5

The source code for javarosa is at: https://bitbucket.org/m.sundt/javarosa
That contains the code that reads and writes the XML.

This is likely an issue with the DateTime handling within javarosa, and
would not simply be an issue with the reading and writing of the values,
but that is a good place to start.

··· On Mon, Jun 15, 2015 at 9:18 AM, Angelo Lazzari wrote:

Hi,
we need to get this issue solved but knowing is not a high priority bug
for the comunity, we're triyng to solve it by ourselves but we blocked in
the code because we cannot find where the ODK reads from the XML the value,
so we cannot debug correcly the issue.

So, can you kindly tell us where is the point where the app reads a value
and than we will be able to focus on it our debug?

THANK YOU VERY MUCH!
Angelo

El jue., 14 may. 2015 a las 15:14, Tom Smyth (tom@sassafras.coop) escribió:

I believe you are experiencing this issue:

https://code.google.com/p/opendatakit/issues/detail?id=1075

https://groups.google.com/forum/#!searchin/opendatakit-developers/1075/opendatakit-developers/Ds82cwZNwbo/pnqA9Azxux8J

I have plans to fix this but I'm not sure when I'll get time.

On 14 May 2015 at 06:10, Angelo Lazzari lazzari.angelo@gmail.com wrote:

Hi all,
sorry, there is a wrong step in my explication: you firstly have to save
and than check the instance file. Sorry.

Thank you very much
Angelo

El jue., 14 may. 2015 a las 12:05, Angelo Lazzari (< lazzari.angelo@gmail.com>) escribió:

Hi everybody,
we think we have a bug in the time field:
the GMT value is lost when

To replicate the bug you can load the attached form and behave as
follow:

  1. reach the time field and put an hour you want (or the one it
    preloads). If you check the instance output XML we can see the correct hour
  • the GMT value, in our case GMT +2.
  1. Press the back button, save the form, than, from the main app menu,
    reload the form you were filling, go to the hour field: YOU CAN SEE THE
    FIELD CHANGED HIS VALUE TO AN HOUR LESS THAN THE PREVIOUS VALUE, and if you
    continue to do the same thing (exiting and entering the form) you'll loose
    an hour every time.

Could be a bug? Or we're missing something?

We tried the last odk collect app and the problem is still there.

Thank you very much
Angelo

--
You received this message because you are subscribed to the Google
Groups "ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google
Groups "ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Tom Smyth

Worker-Owner, Sassafras Tech Collective
Specializing in innovative, usable tech for social change
sassafras.coop · @sassafrastech

Resident, Touchstone Cohousing
touchstonecohousing.org

--
You received this message because you are subscribed to the Google Groups
"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups
"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com