QField icon indicating copy to clipboard operation
QField copied to clipboard

can not save a float number

Open tobair opened this issue 5 years ago • 11 comments

The problem is, if a decimal number is to be stored (e.g. '1.5') the value changes to '15.'.

Reproduction Steps:

  1. Make a QGIS Project with a Geopackage (Geom: Point, Attribute: length (real))
  2. Copy the Project to the tablet
  3. Try to chance the attribute length
  • QField version: 1.7.6
  • Android Version 10

tobair avatar Nov 27 '20 21:11 tobair

@tobair I cannot reproduce on older Android, but most probably I have different configuration from yours.

Did you start experiencing this issue since 1.7.6, or you always had this issue? What language do you use on your android device? Can you please share the exact project you use to have this error, or at least the configuration you use for that field in Layer Properties -> Attributes Form?

suricactus avatar Dec 02 '20 01:12 suricactus

The QField project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale". If you would like to continue with this issue, please provide any missing information or answer any open questions. If you could resolve the issue yourself meanwhile, please leave a note for future readers with the same problem and close the issue. In case you should have any uncertainty, please leave a comment and we will be happy to help you proceed with this issue. If there is no further activity on this issue, it will be closed in a week.

github-actions[bot] avatar Dec 16 '20 02:12 github-actions[bot]

double_field_qfield

signedav avatar Dec 21 '20 11:12 signedav

The QField project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale". If you would like to continue with this issue, please provide any missing information or answer any open questions. If you could resolve the issue yourself meanwhile, please leave a note for future readers with the same problem and close the issue. In case you should have any uncertainty, please leave a comment and we will be happy to help you proceed with this issue. If there is no further activity on this issue, it will be closed in a week.

github-actions[bot] avatar Jan 05 '21 02:01 github-actions[bot]

No stale. This is still the case.

signedav avatar Jan 05 '21 07:01 signedav

I can confirm this bug with the following setup: QField 1.8.1 Samsung Tab Active3 Android 10

Doesn't happen on QField: 1.6.4 Samsung Tab Active2 Android 9

soester avatar Jan 13 '21 13:01 soester

This bug still persists in Qfield 1.9.0

soester avatar Mar 18 '21 12:03 soester

Switching from default Samsung Keyboard to AnySoftKeyboard resolves the issue...

soester avatar Apr 13 '21 15:04 soester

Thanks, since the A Tab2 is used here, too. Was it a language problem then? Maybe the decimal separator was wrong? Or just plain crappy preinstalled stuff...

Marwe avatar Apr 25 '21 12:04 Marwe

Switching from Samsung Keyboard to GBoard also fixes the problem. Qfield v1.9.6 on Samsung Galaxy S10, Android version 11.

troussell avatar Sep 29 '21 12:09 troussell

Hi,

This bug still on Qfield 2.5.5 on Samsung tab, with Samsung Keyboard. Solved by changing the keyboard (GBoard).

I also tested it on an iphone 12 - iOS 15.6.1 / Qfield 2.5.5. The keyboard only accepts comma, while the form only accepts points as decimal separator.

MicrosoftTeams-image

sallib avatar Dec 19 '22 10:12 sallib

@sallib , can you check with the latest QField version on the play store, we fixed handling of floating number parsing in the last version.

nirvn avatar Feb 01 '25 11:02 nirvn

I've just tested it and it works! Thanks !

sallib avatar Feb 03 '25 09:02 sallib

@sallib , that's a fantastic news, thanks for taking the time to reporting this back. Happy field mapping!

nirvn avatar Feb 03 '25 09:02 nirvn