View Revisions: Issue #1679

Summary 0001679: Request that the Dispatcher optionally take a DispatcherPriority parameter
Revision 2020-05-04 22:08 by DavidYawCSpeed
Description There's a feature of the WPF dispatcher that I wonder if Noesis could provide for their Dispatcher.

On the WPF Dispatcher, BeginInvoke can optionally take a parameter of type DispatcherPriority. This allows you to specify when the delegate gets executed, so it can be prioritized properly with respect to other things. In particular, you can say whether the delegate should be higher or lower priority than rendering, user input, etc.

If their dispatcher already has this concept of priorities, it would be nice if they exposed a way to specify which priority level the delegate should be executed at. If the Noesis Dispatcher doesn't have the concept of priorities the way that the WPF one does, then no change.

https://docs.microsoft.com/en-us/dotnet/api/system.windows.threading.dispatcher.begininvoke
https://docs.microsoft.com/en-us/dotnet/api/system.windows.threading.dispatcherpriority
Revision 2020-05-04 19:22 by darthmaule2
Description There's a feature of the WPF dispatcher that I wonder if Noesis could provide for their Dispatcher.

On the WPF Dispatcher, BeginInvoke can optionally take a parameter of type DispatcherPriority. This allows you to specify when the delegate gets executed, so it can be prioritized properly with respect to other things. In particular, you can say whether the delegate should be higher or lower priority than rendering, user input, etc.

If their dispatcher already has this concept of priorities, it would be nice if they exposed a way to specify which priority level the delegate should be executed at. If their dispatcher doesn't work this way, then no change.

https://docs.microsoft.com/en-us/dotnet/api/system.windows.threading.dispatcher.begininvoke
https://docs.microsoft.com/en-us/dotnet/api/system.windows.threading.dispatcherpriority