I have a simple problem. How do you clear the text in a Text Input widget such that the HINT text re-appears.
I tried writing a “” but that does nothing e.g. Blynk.virtualWrite(V1, "");
I tried putting in a space i.e " " e,g,. Blynk.virtualWrite(V1, " "); but the HINT does not re-appear as their is a space int he INPUT.
Anyone know any tricks - nothing I can see in the docs ?
would have thought something as simple as this could be done by the Blynk team during a morning coffee break - seems pretty simple but then again I would assume they have a list of 100’s of other simple things on the to do backlog
from a customer experience perspective i’ve found that a user can get quite confused with the text widget.
i.e. you need to press enter for it to register and fire off a BLYNK_WRITE() which makes sense. However I am not able to clear the field so that the HINT re-appears. Therefore when the user comes back they see the same text populated but they don’t know (or is not very obvious) they need to select it and press enter for it to be processed.
Hope I’m making sense in terms of what I’m trying to convey. I’m thinking if there was a way for pragmatically being able to clear the text field such that the HINT re-appeared would be great.
I understand what you are describing, thanks for sharing it. But as I stated above, Text Input widget serves a different purpose and works as expected.
To cover your use-case, a different widget is needed and we don’t have it now. Please create a request on our shared roadmap board.
Or… just maybe add in a toggle to allow (normal) clearing of the input field while sending the text to the device upon pressing enter. Why need yet another widget, requiring voting, pleading and whatnot. Even with my modified coding, i simply never use that current widget because of its strange crippling “Intended feature”
It is like having one button widget that you can only press ON…
Outside of possible commercial specific use, I highly doubt that such a crippling feature is needed A normally operating text input widget would do all of those things as well… as evidenced in any text input based control I have ever used.
“Took to long to backspace to your next move… you were eaten by a grue.”