Describes the priorities at which operations can be invoked by way of the Dispatcher.
Assembly: WindowsBase (in WindowsBase.dll)
XMLNS for XAML: Not mapped to an xmlns.
|The enumeration value is 2. Operations are processed when the application is idle.|
|The enumeration value is 4. Operations are processed after all other non-idle operations are completed.|
|The enumeration value is 3. Operations are processed after background operations have completed.|
|The enumeration value is 8. Operations are processed at the same priority as data binding.|
|The enumeration value is 0. Operations are not processed.|
|The enumeration value is 5. Operations are processed at the same priority as input.|
|The enumeration value is -1. This is an invalid priority.|
|The enumeration value is 6. Operations are processed when layout and render has finished but just before items at input priority are serviced. Specifically this is used when raising the Loaded event.|
|The enumeration value is 9. Operations are processed at normal priority. This is the typical application priority.|
|The enumeration value is 7. Operations processed at the same priority as rendering.|
|The enumeration value is 10. Operations are processed before other asynchronous operations. This is the highest priority.|
|The enumeration value is 1. Operations are processed when the system is idle.|
There is no specific system state or "idleness" corresponding to and in the current version of WPF. Both are still valid priorities; therefore, an operation with a priority of has a higher priority than an operation with a priority of .
The Dispatcher does not throttle the execution of an operation if it exceeds a certain percentage of the CPU. One way to throttle a process it to use a timer.
The following example is a call to BeginInvoke that passes a delegate which accepts an argument. The priority is set to .