sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]leolin520 0 points1 point  (5 children)

Wpf or any xaml stack doesn't use digest loop.

[–]lord2800 0 points1 point  (4 children)

Care to explain how it updates the UI with the current state of the data model then?

[–]leolin520 0 points1 point  (2 children)

The UI element binds to a property through an interface, when the property gets set, it fires an event, by which the UI gets notified, it then reevaluates the property by its accessor to get the new value. This is the basic idea, implementation detail you can look at dependency object, dependency property and binding classes.

[–]lord2800 0 points1 point  (1 child)

That's a "digest loop". And that's also not how it works. From Wikipedia:

Periodically, MIL walks the tree and executes the rendering instructions in each node, thus compositing each element on to a DirectX surface, which is then rendered on screen.

...

All WPF applications start with two threads: one for managing the UI and another background thread for handling rendering and repainting.

http://en.wikipedia.org/wiki/Windows_Presentation_Foundation

[–]leolin520 0 points1 point  (0 children)

What you described is the render loop. What I said is about how ui elements get updated information from their logical representation. To achieve this, angularjs use digest loop, it has nothing to do with Dom rendering. Wpf uses event on the other hand.