You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: xml/System.Windows.Threading/DispatcherPriority.xml
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@
22
22
## Remarks
23
23
There is no specific system state or "idleness" corresponding to `ApplicationIdle` and `ContextIdle` in the current version of WPF. Both are still valid priorities; an operation with a priority of `ContextIdle` has a higher priority than an operation with a priority of `SystemIdle`.
24
24
25
-
The <xref:System.Windows.Threading.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.
25
+
The <xref:System.Windows.Threading.Dispatcher> does not throttle the execution of an operation if it exceeds a certain percentage of the CPU. One way to throttle a process is to use a timer.
26
26
27
27
If an operation is posted using <xref:System.Windows.Threading.Dispatcher.Invoke%2A?displayProperty=nameWithType> on its own <xref:System.Windows.Threading.Dispatcher> at a priority of `Send`, the operation bypasses the queue and is immediately executed.
0 commit comments