Every time I use actionButtons to fill textboxes/textareas (via renderUI()) I have an issue that those text fields don't always update. I'll bring couple of examples:
I use a drop-down list and "Add" actionButton to fill a textbox. Let's say I have "abc" selected in a drop-down list. I press "Add", so textbox gets a value "abc", then modify the textbox contents (e.g. make it "abcd"), press "Add" again, but the content is still "abcd".
I have a textarea with "Save" and "Load" buttons, which save and load data to/from a text file. Let's say I load some data into the textbox, then modify it and press "Load" again to get the initial data, as my modifications were incorrect. But I can't do that, as textarea doesn't get updated.
Currently I use the following fix. Inside renderUI() I save the previous value of the textbox to some environment that I keep specifically for such cases, so every time I generate new contents for the textbox I check if the value is the same as the previous value. If it is the same, I either add a space at the end and remove it if there is already a space at the end.
It would be useful if you could fix this problem in some next release. Absolutely all my GUIs face this issue and have this ugly fix.
The text was updated successfully, but these errors were encountered:
The value field of the element doesn't change when the user types in the box. When the HTML code is re-sent to the browser, Shiny doesn't bother updating the object since the HTML code is exactly the same.
Every time I use actionButtons to fill textboxes/textareas (via renderUI()) I have an issue that those text fields don't always update. I'll bring couple of examples:
Currently I use the following fix. Inside renderUI() I save the previous value of the textbox to some environment that I keep specifically for such cases, so every time I generate new contents for the textbox I check if the value is the same as the previous value. If it is the same, I either add a space at the end and remove it if there is already a space at the end.
It would be useful if you could fix this problem in some next release. Absolutely all my GUIs face this issue and have this ugly fix.
The text was updated successfully, but these errors were encountered: