No results found
See original GitHub issueHi There,
i am trying to implement this awesome Multiselect ComboBox. I followed the examples and have following setup Inside my ViewModel I used the LanguageItem Class with all the Interfaces
`
var group = new LanguageItemGroup(0, "All Items");
Items = new ObservableCollection<LanguageItem>
{
new LanguageItem
{
Id = "en-US",
Name= "English (United States)",
Group = group
},
new LanguageItem
{
Id = "it-IT",
Name= "Italian (Italy)",
Group = group
},
new LanguageItem
{
Id = "de-DE",
Name= "German (Germany)",
Group = group
}
};`
My Items ObservableCollection looks like this
public ObservableCollection<LanguageItem> Items { get => _items ?? (_items = new ObservableCollection<LanguageItem>()); set { _items = value; OnPropertyChanged("Items"); } }
Inside XAML i used this Code
<sdl:MultiSelectComboBox DataContext="{Binding }" ItemsSource="{Binding Items}" IsEditable="true" SelectionMode="Multiple"/>
The Items Collection is correctly called and returns the 3 Items i initialized in the viewmodel, but the MultiSelectComboBox only shows “No results found”
Issue Analytics
- State:
- Created 3 years ago
- Comments:13 (5 by maintainers)
I am encountering the same issue. Able to see the items bound to the control via itemsource in code using breakpoints but the combobox shows “No results found”. Was working perfectly in v1.0.16, updated to v1.0.18 and this issue pops up. Reverted back to 1.0.16 and its showing the items in dropdown list fine. Update- Tried with v1.0.17 also, it also works fine.
BTW Another infinite loop issue that i was facing with 1.0.16 & 1.0.17 if assigning itemsources to the comboxes after wpf’s initialize components in main initialisation seems to be resolved in 1.0.18. Came to raise an issue for it when i noticed the update and did that to end up with this issue…
Hello @Impertatore, Thanks a lot for the prompt reply. As suggested assigning data context after data tree is available by subscribing to the window’s event handler worked perfectly and it appears to be a different issue due to incorrect implementation on my end. Please close this issue back again, thank you!