WPF example is behaving weirdly
See original GitHub issueHi there,
First let me thank you for the massive and impressive work you did with this library! Observable collections are really something that should get more love in the .Net ecosystem 😃
I noticed something strange with the WPF example that you provide. When I run it locally and press a few times on the “Insert” button, I get the following :
The first 3 lines (in red) correspond to the initial items inserted via AddRange
and is the tuple (value, view)
, while the rest (in green) has been added by pressing the “Insert” button and is only the value.
I do not understand why there is a difference, do you have any idea what could be the reason?
I’m also questioning yielding tuples (value, view)
when enumerating, instead of only views. Tuples cannot be used directly for <ListView ItemSource={...} />
. Is there a reason for this choice?
Issue Analytics
- State:
- Created 2 years ago
- Comments:11 (7 by maintainers)
Top GitHub Comments
sorry for no longer repond it, I’ll check it.
This issue needs to be resolved to make the library usable with WPF bindings.
Sending either a tuple or the actual object makes it unusable with ListView or DataGrid controls since the column bindings completely break. One way around this is tediously implementing IValueConverters for each column that extract the desired property from either a tuple or the object.