Hi Thomas,

I implemented the changes into Crosslight FormBuilder sample and follow the steps below:

1. After the form appear, the Amount field is empty, showing only the placeholder text ("Amount").
2. Then enter an amount, 123.45.
3. Leave the field.
4. Get back to the amount field and clear the amount.

No error persist when performing the above steps. For your information, I'm using Crosslight 5.0.5000.626-experimental from NuGet.

If you are using the latest stable version (5.0.5000.607), could you please try to update the NuGet package and let me know the result?

Hello Yudi,

I downloaded the FormBuilder sample but I could not find the code you changed. Searching for a nullable, I just found a DateTime?.

So, I upgraded my code with Crosslight 5.0.5000.626-exp, but nothing changed. I still get the errors. Maybe it is a cultural problem, too. The decimal delimiter can be "." (123.45) or "," (123,45). I think you have to include this in the conversion code.

Thanks,

Thomas

I downloaded the FormBuilder sample but I could not find the code you changed.

Sorry if my previous reply causing misunderstanding. Here are the detail steps that I did to test the reported problem:

1. Open Crosslight FormBuilder sample in Xamarin Studio or Visual Studio.
2. Open TextField.cs (FormBuilderSamples.Core/Models/Reference/Editors/TextField.cs).
3. Make changes into the class by adding: "Amount" nullable property; add contants AmountPropertyMetadata; and initialize Amount property to null in the contructor.
4. Open TextField.Form.cs (FormBuilderSamples.Core/Models/Reference/Editors/TextField.Form.cs).
5. Make changes into the class by: enabling DetailOnlySection; add Amount metadata into the DetailOnlySection.
6. Save the changes.
7. Test the project on LG Nexus 4 running Android 5.1.1 Lollipop.

I enclosed the video which shows how the test was conducted on my device. Please find the video and the modified sample in the attachment and let me know if you find anything that I might miss during my attempt to reproduce the reported problem.

Note: The modified sample is uploaded in here.

Hello Yudi,

this may work at your end and with your settings, but it does not work with my settings.

Unfortunately, I cannot record my screen like you do, so I try to describe as good as I can.

The first time I enter 123.50 into the empty Amount field. Then I set the focus to the text field above. No error and value stays as I entered it. I set the focus to the Amount field again. Then I clear the Amount field and set the focus to the text field above. The Amount field is now not empty. It shows 123,50 (! comma as decimal delimiter).

I think, this has to do with the culture settings as I wrote some posts before. My culture is German. Having different culture settings can cause problems when converting values. In one culture the dot (.) is the decimal delimiter and in another culture the comma (,) is the decimal delimiter. When you internally do a conversion and maybe a "TyrParse" you must handle this. Not matter what the decimal delimiter is, the conversion must not fail.

Please, try again with a different culture.

Thanks,

Thomas

Hello Thomas,

Thank you for the detail explanation. I have re-test the scenario and make sure that the test device using German culture (set Settings > Language & input > Language to "Deutsch").

However, no error persist after clear the "Amount" field and set the focus to the text field above.

I have created a worklog for the Crosslight-Android development team to correctly show null value after "Amount" field is cleared. The report is filed under CROS-1128.

I'll keep this thread updated with any news I heard from the team regarding the progress of CROS-1128.

Edited on May 9, 2016 3:30 AM
Reason: Update recent progress of CROS-1128

Nightly-build hotfix for CROS-1128 is now available in NuGet. Per my test, user are now be able to clear the "Amount" field and left the field empty (not revert back to previous valid value) when set the focus to the text field above.

Please give it a spin and let us know how it works in your end.

Hello Yudi,

I applied the hotfix and tested again. The problem seems to be solved. Using my culture it works as intended. Hopefully it works in any other culture as well.

Thanks,

Thomas

Glad to hear the good news.

Should you need further assistance or run into any problems regarding our controls, feel free to post it into our forum. We would be happy to assist you again.