Reply to comment

Yes, it is worth suppressing non-change events

Comments are welcome here, but you can also post to http://updatecontrols.codeplex.com/discussions

Absolutely, it is worth suppressing non-change events. If the setter calls OnSet(), then it triggers all related dependent updates. If the value hasn't actually changed, this would result in the same dependent values being recalculated (assuming determinism, which is required for this algorithm to work anyway). This is a great optimization.

Unfortunately, there is no way to suppress changes to dependents. If an independent changes, but a direct dependent produces the same result, indirect dependents will still fire.

That documentation set was hard to maintain and not entirely useful, so I took it down a couple of years ago. I'll have to remove all links to it.

Reply

By submitting this form, you accept the Mollom privacy policy.