-
Notifications
You must be signed in to change notification settings - Fork 762
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Add support to ObserveOn WinUI 3's DispatcherQueue. #1651
Comments
@dojo90 FYI ReactiveUI has a Scheduler implementation for DispatcherQueue now. |
It's nearing the end of 2023 now and all the reading I've done between documentation and GitHub issues for Reactive Extensions, MS.UI.Xaml repo, Windows Runtime SDK does not help me figure out how to observe on my app's dispatcher thread. Trying |
@andrensairr Just copy+paste this if you aren't using ReactiveUI |
Thank you @kmgallahan, that seems to do the trick just fine. Not using ReactiveUI just yet, I've a fair bit of work to do before sorting the finer points of my UI and I wasn't sure how complete the WinUI 3 support in ReactiveUI was just yet. |
@andrensairr I recently decided to stop using ReactiveUI in favor of just System.Reactive & DynamicData. If you aren't developing a cross-plat app, which I was not, then I found the prescriptive nature to be restrictive. I just extracted the most useful bits I was using (DispatcherQueueScheduler, DisposeWith), and switched from WhenAnyValue to the change notifications offered by DynamicData. |
Feature request
Rx.NET v5.?.?
Windows / WinUI 3
Anyone using Rx with WinUI 3 would likely find this useful this at some point.
This is a request to add ObserveOn extension method(s) to accept WinUI 3's Microsoft.UI.Dispatching.DispatcherQueue for scheduling.
Might be pertinent to start by introducing a new HAS_WINUI conditional compilation symbol. The Target framework wouldn't work as a differentiator, but every project file must contain
<UseWinUI>true</UseWinUI>
, so that could work.The text was updated successfully, but these errors were encountered: