Timeline for ListView MultiSelect, MVVM and RoutedCommands
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 10 at 17:48 | history | edited | Sᴀᴍ Onᴇᴌᴀ ♦ | CC BY-SA 4.0 |
update spelling, formatting
|
| Oct 1, 2013 at 13:27 | comment | added | Mathieu Guindon | I meant this:stackoverflow.com/questions/19100882/… | |
| Oct 1, 2013 at 6:14 | comment | added | Nikita B | @retailcoder, yes, you should either set an actual DataContext in Xaml or specify a design-time DataContext (see stackoverflow.com/questions/13863099/… for example). Normally it doesn't worth the effort tho. | |
| Oct 1, 2013 at 6:06 | history | edited | Nikita B | CC BY-SA 3.0 |
deleted 22 characters in body
|
| Sep 30, 2013 at 17:21 | vote | accept | Mathieu Guindon | ||
| Sep 30, 2013 at 17:21 | comment | added | Mathieu Guindon |
Wow this is amazing - turns out I have those "item view models" implementing a ISelectable interface so they all have a IsSelected property, and with this XAML I can perform that binding at item level, only the designer blue-squigles {Binding IsSelected} saying it can't resolve that property.. but it works! Is there a way to make the ListView.ItemContainerStyle block understand that the view model it should validate at design-time against is that of ListView.ItemsSource? (like ListView.ItemTemplate does) ...'cause for a novice dev it's not obvious that it works at run-time!
|
|
| Sep 30, 2013 at 7:12 | history | answered | Nikita B | CC BY-SA 3.0 |