fix: Replace default `MainThreadScheduler` on UAP #2100
What kind of change does this PR introduce?
What is the current behavior?
Of course, in these situations most devs will simply inject a scheduler into their view models for anything that used on a separate window. But this still won't block the hijacking because if code from the main window is ever executed on the thread separate window and then attempts to get an instance of
Since that is a very likely scenario in Rx, the problem should be solved in ReactiveUI.
What is the new behavior?
It also does not use
What might this PR break?
Please check if the PR fulfills these requirements
A separate PR will be added to the website documentation to make it VERY clear that ReactiveUI supports one window UWP environments only out of the box and suggest appropriate workarounds for multiple windows.
@glennawatson I did give a multiple window scheduler the good ole' college try but after about a week of testing I do not think it's possible. See an attempt here: https://gist.github.com/hinterlandsupplyco/c8e0396f6d837fdc9cd2a5b00688b451
worldbeater left a comment •
Just tried the new