If I make this call from the device:
Blynk.virtualWrite(ValueDisplay_VPIN, "40d");
In the mobile app it doesn’t display like that. The app ValueDisplay field shows
40.0
However, if I send the string “40s”, it displays exactly as I sent it.
If this is expected, then I need to see documentation on what kinds of built-in formatting exist, and how to use them, or disable them.
The documentation you pointed to is for Labeled Value, not Value Display. Even so, I see no formatting notations that would include the letter ‘d’.
Yep, Value Display does not support formatting, but Labeled Widget supports it and it should be configured in the widget’s settings - please check the above link on how to setup float’s formatting.
LOL…that’s the whole point of my original post. The Value Display is doing some formatting of some kind, and I don’t want any formatting. Just try this yourself:
String x = "40d";
Blynk.virtualWrite(YourValueDisplay_VPIN, x);
That should just display as “40d”, but it will display as “40.0”.
ou, i’ve got your point - i should stop commenting late at night) @vshymanskyy do we have some documentation on such behavior on library side?
AFAIK there is no formatting.
What does the following do on your system?
Blynk.virtualWrite(ValueDisplay_VPIN, String("40d"));
The library is not applying any conversions to the strings.
@Costas same thing. I included screenshots below so there is no confusion about what is showing.
Blynk.virtualWrite(V125, String("40d"));
Actually, this is the valid double number on Android. When value comes to android it is parsed with native class Double.parseDouble("40d"); and 40d is valid double number so it is parsed as it was just 40.0.
Ouch! So if a string could be parsed into a double, it will be, but otherwise it displays the unmodified string. That little detail should appear in the docs.
Edited to remove my question and replace it with this answer:
The “40d” displays correctly in a Labeled Value and terminal controls.
Correct.
