Preventing parent re-renders or preventing input fields from losing their current value on re-render
Hi all.
I have a Solara application where there is a separate thread (using solara.thread) that periodically performs some work and updates a text component, at some interval. In addition, there are some other components that use solara.InputInt/solara.InputFloat/solara.InputText that the user can interact with.
However, if the user is in the middle of inputting a value (the cursor is located in the Input component) and the thread runs its work and updates its text component, the current value of the Input component is resetted. This makes it very hard to input values if the thread runs at .e.g. once every second, as it will just reset the value the user tries to input.
I know that there is a parameter called "continuous_update=True" that will set the value of the Input component for every single character inputted, but the problem is that this, in turn, would trigger a huge amount of updates in other places of my application, which I would want to avoid (e.g. a text field might contain 50 characters, which would mean 50 updates).
I have attached some python code with an small example that shows the problem. You can run it with "solara run example.py".
If you try to input an integer into the first IntInput, your progress will be lost every second, so you need to be very quick when inputting the value. I have also added some debug prints to show when a component is updated, and it actually seems like the input components are not updated when the thread is running, but even still the progress seems to be lost? I don't understand that.
This problem (so far) only occurs with solara.InputInt/solara.InputFloat/solara.InputText, and other types of components behave as expected.
Can I avoid a child component (TimerComponent in my example) from resetting the value of other Input components in the parent component?
Thanks beforehand for reading
Python: 3.11.7
Solara: 1.39.0
I have a Solara application where there is a separate thread (using solara.thread) that periodically performs some work and updates a text component, at some interval. In addition, there are some other components that use solara.InputInt/solara.InputFloat/solara.InputText that the user can interact with.
However, if the user is in the middle of inputting a value (the cursor is located in the Input component) and the thread runs its work and updates its text component, the current value of the Input component is resetted. This makes it very hard to input values if the thread runs at .e.g. once every second, as it will just reset the value the user tries to input.
I know that there is a parameter called "continuous_update=True" that will set the value of the Input component for every single character inputted, but the problem is that this, in turn, would trigger a huge amount of updates in other places of my application, which I would want to avoid (e.g. a text field might contain 50 characters, which would mean 50 updates).
I have attached some python code with an small example that shows the problem. You can run it with "solara run example.py".
If you try to input an integer into the first IntInput, your progress will be lost every second, so you need to be very quick when inputting the value. I have also added some debug prints to show when a component is updated, and it actually seems like the input components are not updated when the thread is running, but even still the progress seems to be lost? I don't understand that.
This problem (so far) only occurs with solara.InputInt/solara.InputFloat/solara.InputText, and other types of components behave as expected.
Can I avoid a child component (TimerComponent in my example) from resetting the value of other Input components in the parent component?
Thanks beforehand for reading
Python: 3.11.7
Solara: 1.39.0
example.py935B
