Skip to content
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

[Bug]: DevExpress and ReactiveUI Binding PropertyChanged event Not processed #3979

Open
hackerhui opened this issue Feb 27, 2025 · 0 comments
Labels

Comments

@hackerhui
Copy link

Describe the bug 🐞

When attempting to bind for instance a GridControl or TreeListControl's SelectedItem property through the ReactiveUI preferred way of setting up bindings, it does not work:

Step to reproduce

This issue occurs because the Reactive UI framework supports notifications raised by the INotifyPropertyChanged interface. Unlike the standard WPF ListBox element, our GridControl implements the INotifyPropertyChanged interface. Reactive UI's binding mechanism determines this fact and tries to handle the PropertyChanged event for all properties. However, it seems not to take into account that this event can be raised for dependency properties as well. As a result, when GridControl's SelectedItem property is changed, Reactive UI's binding mechanism catches the PropertyChanged event for this property and tries to work with it as with a simple property but not as with DependencyProperty and doesn't update bindings.
By the way, you can easily check this scenario with the standard WPF ListBox element. It's enough to create a ListBox class descendant, which implements the INotifyPropertyChanged interface:

Reproduction repository

https://github.com/reactiveui/ReactiveUI

Expected behavior

about:
https://supportcenter.devexpress.com/ticket/details/t728347/devexpress-and-reactiveui

Screenshots 🖼️

No response

IDE

No response

Operating system

No response

Version

No response

Device

No response

ReactiveUI Version

No response

Additional information ℹ️

No response

@hackerhui hackerhui added the bug label Feb 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant