Forums | NoesisGUI

Hi all,


I have an indexer which I am successfully binding to, however I am unable to raise a PropertyChangeEvent as I do not know the indexer's property. The suggestions on WPF documentation is "Item[]", and while this doesn't raise an error (I think because the property Item is automatically created for indexers) it doesn't update the binding.

How do I notify of an indexer property change?


Thanks,

Mark

Unfortunately it seems to be a bug, indexer properties are not responding to "Item[]" property changes, only IList collections are doing so right now

Could you please create a ticket in our bugtracker, we will try to solve it as soon as possible.

Will do.

That leaves me in a bad place right now, is the only option I have to create a property for each entry I want to access?

Which kind of keys are you using to access the indexer properties?
If they are ints you can use an ObservableCollection<T>, and if they are strings you can use a ResourceDictionary.

Reported: http://www.noesisengine.com/bugs/view.php?id=753

Which kind of keys are you using to access the indexer properties?
If they are ints you can use an ObservableCollection<T>, and if they are strings you can use a ResourceDictionary.

When I use the indexer, the indexer tries to get the required data using an Id. This data can come over the network, so it cannot be stored in an ObservableCollection or ResourceDictionary, at least not without a lot of questionable coding practices. Unless I am missing something?

Ok, I understand now, if you cannot store the data coming from the network, ResourceDictionary won't be a solution, you are right.

Anyway, we are going to release soon a patch for the last version with the indexer notification issue solved

I have written a bunch of properties to get around the issue for now, which is a lot of duplication really. I am looking forward to having the indexers working.

Thanks for the quick turnaround on the fix.

Solved in 1.2.5f8 released

Ha, I was already wondering whether this was a bug when I tried to use indexer the other week. But I couldn't be bothered and went a different route. But it's good to know it's solved now.