In openHAB-Android 3.21.0-beta I have a sitemap with an Input element, which is used for unformatted text
When I click on the input element, the keyboard is shown and the border colour of the input element changes from white to pink. When I change the text and click afterwards on an a toggle or Switch with mappings=[…], the keyboard is still shown and the border colour remains pink.
I expect, when I click on an element, different from the input element, and the clicked element sends a command, that then the Input element looses focus and the keyboard is hidden.
In any case, the problem report is that there should be an indication, when the text in the input is different from the state of the item, that is the text is changed and the change is not submitted. It looks like the only way to submit a change is to press the OK/Enter button on the keyboard. This is fine, but when I press the OK/Enter button, the keyboard is hidden, the cursor in the input element continues blinking and the border of the input element is pink. When I try now, there is nothing I can do, to change the border of the input element from pink to white and to remove the blinking cursor.
The above describes several problems, or nuances of the same problem, and there are different valid approaches to address it.
I suggest to use different colours for the border of an input element to show three different states:
- not focused
- focused and the content of the input element is identical to the state of the item. That is either the state of the item was not changed within the input box, or it was changed and the change was submitted.
- focused, the content of the input is different from the state of the item. This happens for example when the user has changed the text, but the user has not yet submitted the text.
This problem seems related to autoupdate=“false”, and it is related, but it exists independent of autoupdate="false’. Even if the item value is changed instantly by the server, because it is just stored in a database by openHAB, the user does not see a difference between changing an item, without submitting its value to the server, and changing a value and submitting its value to he server.
In openHAB-Android 3.21.0-beta I have a sitemap with an
Inputelement, which is used for unformatted textWhen I click on the input element, the keyboard is shown and the border colour of the input element changes from white to pink. When I change the text and click afterwards on an a toggle or Switch with
mappings=[…], the keyboard is still shown and the border colour remains pink.I expect, when I click on an element, different from the input element, and the clicked element sends a command, that then the Input element looses focus and the keyboard is hidden.
In any case, the problem report is that there should be an indication, when the text in the input is different from the state of the item, that is the text is changed and the change is not submitted. It looks like the only way to submit a change is to press the OK/Enter button on the keyboard. This is fine, but when I press the OK/Enter button, the keyboard is hidden, the cursor in the input element continues blinking and the border of the input element is pink. When I try now, there is nothing I can do, to change the border of the input element from pink to white and to remove the blinking cursor.
The above describes several problems, or nuances of the same problem, and there are different valid approaches to address it.
I suggest to use different colours for the border of an input element to show three different states:
This problem seems related to
autoupdate=“false”, and it is related, but it exists independent ofautoupdate="false’. Even if the item value is changed instantly by the server, because it is just stored in a database by openHAB, the user does not see a difference between changing an item, without submitting its value to the server, and changing a value and submitting its value to he server.