minor
This commit is contained in:
parent
f2328f035f
commit
6b9515ffd0
1 changed files with 2 additions and 2 deletions
|
@ -12,13 +12,13 @@ Let's check the real-life application to better understand that requirement and
|
|||
|
||||
**For instance, we want to track mouse movements.**
|
||||
|
||||
In browser we can setup a function to run at every mouse micro-movement and get the pointer location as it moves. During an active mouse usage, this function usually runs very frequently, can be something like 100 times per second (every 10 ms).
|
||||
In browser we can setup a function to run at every mouse movement and get the pointer location as it moves. During an active mouse usage, this function usually runs very frequently, can be something like 100 times per second (every 10 ms).
|
||||
|
||||
**The tracking function should update some information on the web-page.**
|
||||
|
||||
Updating function `update()` is too heavy to do it on every micro-movement. There is also no sense in making it more often than once per 100ms.
|
||||
|
||||
So we'll assign `throttle(update, 100)` as the function to run on each mouse move instead of the original `update()`. The decorator will be called often, but `update()` will be called at maximum once per 100ms.
|
||||
So we'll wrap it into the decorator: use `throttle(update, 100)` as the function to run on each mouse move instead of the original `update()`. The decorator will be called often, but `update()` will be called at maximum once per 100ms.
|
||||
|
||||
Visually, it will look like this:
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue