What is the performance overhead I have to pay for using rapidUI?
In real-world scenarios the performance overhead should be neglible. In some situations the rapidUI may actually perform faster than an OnIdle based scheme. OnIdle calls are evaluated everytime the UI becomes idle. This can consume considerable resources, especially when the user interface consists of several hundred controls. rapidUI on the other hand only evaluates those properties, rules and controls that have actually changed or depend on a value that has changed.