ReactiveCommand.Subscribe not running in UI thread?!

[Atle]

Hi!

I thought that subscribing to a ReactiveCommand should invoke the subscription in the UI thread? For some reason it is usually invoked in a worker thread even though the command is invoked in the UI thread.

This is what triggers the command:

in Constructor:

SeriesCollection = new ObservableCollection<IChartSeriesViewModel>();

ReactiveCommand.CreateAsyncTask(async _ =>

{

    ....

    var data = await getDataAsync(); <--- All except this must run in UI

    .... 

    (Create view models from data)

    ....    

    return viewModels;

}

CreateSeries.ObserveOn(RxApp.MainThreadScheduler).Subscribe(x =>

{

    SeriesCollection.Clear(); <------------------- Crash due to invoked by worker thread which is not owner of the SeriesCollection object.

    foreach (var chartSeriesViewModel in x)

        SeriesCollection.Add(chartSeriesViewModel);

    YRange = CalculateYRange(x);

});

Listen to a property changed event of the background model

IDisposable selectedAnalysisSubscription =

                this.WhenAnyValue(x => x.Model.SelectedIdentifierPropertyPair)

                     .ObserveOn(RxApp.MainThreadScheduler)

                     .InvokeCommand(CreateSeries);

How do

[Atle]

Seems like the RxApp.MainThreadScheduler is not set up correctly.

Adding this on startup seems to fix the issue:

RxApp.MainThreadScheduler = DispatcherScheduler.Current;

RxApp.TaskpoolScheduler = TaskPoolScheduler.Default;

- Atle

[paul....@gmail.com]

Platform?

Paul

--
You received this message because you are subscribed to the Google Groups "ReactiveUI mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to reactivexaml...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Atle]

Windows WPF compiled from source and strong named due to being a plug-in to another application. The host application seems to be using Rx as well, and I am getting some "different versions" redirect errors to System.Reactive.Windows.Threading. Not sure if this has anything to do with this.

- Atle

[paul....@gmail.com]

I think all of your problems are because of the strong naming, because you didn’t patch this:

https://github.com/reactiveui/ReactiveUI/blob/master/ReactiveUI/IDependencyResolver.cs#L33

Best,

Paul

[Vladimir Morozov]

Could you please clarify which patch you're talking about?