You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 2, 2023. It is now read-only.
Range is now documented in the ODK XForms spec and in JavaRosa as of v2.2.0 released last weekend. Validate was also updated and on the Collect side, the widgets are on track to ship at the end of June (getodk/collect#105). The issue has been filed on the XLSFrom side as well - XLSForm/pyxform#79. It'd be great to get it in Build!
The text was updated successfully, but these errors were encountered:
* also spruce up bindDisplayIf to check against things other than bools.
* also spruce up validation to not validate if the property isn’t shown.
* still need to update opendatakit/build2xlsform for this feature.
issa-tseng
added a commit
to issa-tseng/odkbuild
that referenced
this issue
Jul 18, 2017
* default values were floats rather than strings. when one edits the
textbox it drops strings in, so we should emulate that.
* zero and negative values should not be permitted for step.
issa-tseng
added a commit
to issa-tseng/odkbuild
that referenced
this issue
Jul 25, 2017
… type.
* so infer int or decimal from the step.
* we already validate that the step is a positive number that divides
the range evenly so don’t bother rechecking that.
* should close out this PR.
Range is now documented in the ODK XForms spec and in JavaRosa as of v2.2.0 released last weekend. Validate was also updated and on the Collect side, the widgets are on track to ship at the end of June (getodk/collect#105). The issue has been filed on the XLSFrom side as well -
XLSForm/pyxform#79. It'd be great to get it in Build!
The text was updated successfully, but these errors were encountered: