You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Firstly - thanks so much for the new callback context and multi-output features added recently. They have significantly improved the development experience!
In the example app below, I'm using both of the new features. When a button is clicked, both sliders are updated from the same callback, and then the graph is updated based on the sliders. It all works fine, but on every button click the plot callback is actually triggered twice (once for each slider) even though both sliders are updated "simultaneously".
Is there a way to prevent this? In my real app, the plot callback is potentially quite heavy (represented by the time.sleep) and there are more than 2 sliders linked to it, so I'd prefer to only call it once when all of the sliders are updated by one multi-output callback.
Firstly - thanks so much for the new callback context and multi-output features added recently. They have significantly improved the development experience!
In the example app below, I'm using both of the new features. When a button is clicked, both sliders are updated from the same callback, and then the graph is updated based on the sliders. It all works fine, but on every button click the plot callback is actually triggered twice (once for each slider) even though both sliders are updated "simultaneously".
Is there a way to prevent this? In my real app, the plot callback is potentially quite heavy (represented by the
time.sleep
) and there are more than 2 sliders linked to it, so I'd prefer to only call it once when all of the sliders are updated by one multi-output callback.The text was updated successfully, but these errors were encountered: