- "When trait changes trigger a callback that performs a heavy computation, you may want to do the computation as rarely as possible. For instance, if the trait is driven by a slider which has its `continuous_update` set to `True`, the user will trigger a bunch of computations in rapid succession. Debouncing solves this problem by waiting for some time any time the trait value has changed to see if it is going to change again, in which case the callback is not called. If the value does not change after some time, then the callback is called with the last value of the trait. The effect is that the callback is only called when the trait pauses changing for a certain amount of time.\n",
0 commit comments