ReactiveProperty

Bug fix

• Fixing an issue notify wrong StartingIndex from CollectionChanged event of ReadOnlyReactiveCollection<T> that is created from IObservable<T>.
  @toras9000 Thank you for reporting this issue.

Bug fix

• Fixed an issue that could break synchronization between ObservableCollection<T> and ReadOnlyReactiveCollection<T>.

Changes

• Update dependency library version Microsoft.Xaml.Behaviors.Wpf to 1.1.39 from 1.1.31 for ReactiveProperty.WPF.

Buf fix

• InvalidCastException is occurred when accessing CollectionChanged<T>.Value property on a callback method for Subscribe of ReadOnlyReactiveCollection.ToCollectionChanged(). This bug was occurred on only v8.0.0, never occurred on previous versions.

Changes

• Add overload methods of ToFilteredReadOnlyObservableCollection for customize trigger for collection's element status changed. see documentation.
• Improve IFilteredReadOnlyObservableCollection for fixing throwing ArgumentOutOfRangeException when source collection was called Clear method.
• Remove UWP specific package. If you would like to use EventToReactiveProperty and EventToReactiveCommand on UWP, please use v7.x. If UWP support SDK style project file, then I re-enable UWP support.

Build on .NET 6 RC2

Add

• Add overload methods of ToFilteredReadOnlyObservableCollection for customize trigger for collection's element status changed. see documentation

This release was built by .NET 6.0 SDK RC1.

Changes

• Improve IFilteredReadOnlyObservableCollection for fixing #286

This release was built by .NET 6.0 SDK RC1.

Changes

• Improve IFilteredReadOnlyObservableCollection for fixing #286

This version is build on .NET 6 SDK Preview 7.

Changes

• Add ForceNotify method to IReactiveProperty interface.
• Change using Scheduler for calling ICommand#Execute on EventToReactiveCommand from UIThread to ReactivePropertyScheduler.Default.
• Add CallExecuteOnScheduler property to EventToReactiveCommand. If true, EventToReactiveCommand call ICommand#Execute on IScheduler that is set to ReactivePropertyScheduler.Default. If false, no changing thread to call ICommand#Execute. Default is true.

This is a first release build on .NET 6 SDK. New features are not this release.

Changes

• Remove UWP specific feature package because the project was not able to build using dotnet build command, to keep build pipeline simply. I will re-support the UWP package when UWP will support the dotnet tool chain.

Change

• Synchronize between CanExecute status of ICommand and IsEnabled property for controls on EventToReactiveCommand behavior. The feature was implemented by @ruix. Thank you for your contribution, (#261)

• Add ReactivePropertyWpfScheduler. Please use this scheduler for WPF applications. Please see: https://okazuki.jp/ReactiveProperty/getting-started/wpf.html

Add

• Add Reactive.Bindings.CollectionUtilities class for easy to create ObserveElementPropertyChanged, ObserveElementObservableProperty and ObserveElementProperty extension methods for custom collection classes.
  If you want to add the extension methods to your custom collection classes, then please add the methods yourself like ObservableCollectionExtensions.cs

Changes

• Supporting properties that don't throw PropertyChanged events for ObserveProperty method's a property path.

Add

• To fix an error when types that are observed using ObserveProperty change. #248

Supporting Reset CollectionChanged events for IFilteredObservableCollection<T>.

Performance improvements for:

• PropertyChangedAsObservable
• CollectionChangedAsObservable
• CanExecuteChangedAsObservable
• ErrorsChangedAsObservable

This effects many methods that call those methods such as:

• ObserveProperty
• Observe(Add|Remove|Move|Replace|Reset)Changed
• Observe(Add|Remove|Move|Replace)ChangedItems
• ReadOnlyReactiveCollection
• ObserveElementProperty
• ObserveElementObservableProperty
• ObserveErrorInfo
• FilteredReadOnlyObservableCollection

Breaking changes

In the previous behavior, the method used SynchronizationCotext to automatically dispatch threads. This is due to the behavior of FromEvent and FromEventPattern in Reactive Extensions.
The new behavior does not automatically dispatch threads. It depends on which thread the event occurred in.

If you need to switch threads, please do so explicitly using the ObserveOn method.

Performance improvements for:

• PropertyChangedAsObservable
• CollectionChangedAsObservable
• CanExecuteChangedAsObservable
• ErrorsChangedAsObservable

This effects many methods that call those methods such as:

• ObserveProperty
• Observe(Add|Remove|Move|Replace|Reset)Changed
• Observe(Add|Remove|Move|Replace)ChangedItems
• ReadOnlyReactiveCollection
• ObserveElementProperty
• ObserveElementObservableProperty
• ObserveErrorInfo
• FilteredReadOnlyObservableCollection

Breaking changes

In the previous behavior, the method used SynchronizationCotext to automatically dispatch threads. This is due to the behavior of FromEvent and FromEventPattern in Reactive Extensions.
The new behavior does not automatically dispatch threads. It depends on which thread the event occurred in.

If you need to switch threads, please do so explicitly using the ObserveOn method.