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
{{ message }}
This repository has been archived by the owner on Jun 3, 2024. It is now read-only.
If I have a callback that depends on a button and an interval, it is very difficult to tell whether the callback was triggered by the button being clicked or the interval being triggered. With multiple buttons, you can use n_clicks_timestamp to find which was most recently clicked. However, at the moment comparing whether an interval was triggered more recently than a button click is pretty messy. Is it possible to add in that property?
The text was updated successfully, but these errors were encountered:
We have a better solution to this - which has already been merged and will be in the next release: callback context, that directly tells you which input(s) triggered the call plotly/dash#608
I'm not quite ready to say we'll deprecate all the _timestamp props, but I don't think we want to add any more until we see if there are cases the callback context doesn't cover.
dash 0.38 is out with dash.callback_context (note the name - it's still called dash.callback in the changelog). We'll collect discussions about the future of *_timestamp properties in #467
If I have a callback that depends on a button and an interval, it is very difficult to tell whether the callback was triggered by the button being clicked or the interval being triggered. With multiple buttons, you can use
n_clicks_timestamp
to find which was most recently clicked. However, at the moment comparing whether an interval was triggered more recently than a button click is pretty messy. Is it possible to add in that property?The text was updated successfully, but these errors were encountered: