11

What is the difference between $evalAsync and $applyAsync? My understanding is that when I use $evalAsync from a directive, the expression will evaluate before the browser renders.

So as an example, if I wanted to scroll to a particular position on a page but not show the jump to that spot, I could use this to scroll to the position and since it fires before the browser has rendered, this visual bug would be gone.

However, what is the purpose of applyAsync? When is it a good idea to use one over the other?

puopg
  • 563
  • 7
  • 17

2 Answers2

9

The

$evalAsync()

will execute in the current digest

$applyAsync()

in a scheduled one.

If you need details: Ben Nadel or stack here

ggorlen
  • 44,755
  • 7
  • 76
  • 106
Luckylooke
  • 4,061
  • 4
  • 36
  • 49
2

Here is what I have been using $applyAsync for. Basically, I use this as a safe $apply. You know that annoying error when you try to trigger a digest when one is already in progress? If you use $applyAsync, you will get another digest, but it will occur when the current digest cycle has completed.

$applyAsync is also cool since you can batch up a bunch of callbacks to fire within then next digest.

puopg
  • 563
  • 7
  • 17
  • 3
    The OP is asking about the difference between `$evalAsync` and `$applyAsync`. You do not reference `$evalAsync` :( – bobjones Oct 17 '16 at 19:03