Matt

I actually get a compile error when setting both DisplayMemberPath and ItemTemplate with the Orcas build I have. You should never have to set both properties at the same time.

If you want to enable search when ItemTemplate is set, you can set TextSearch.TextPath=”Name” on the ListBox.

We enabled search by default with DisplayMemberPath because it’s really easy for us to know what text you want to use for the search. With ItemTemplate it’s a lot more complicated, so we only enable it when you specify the search path explicitly.

Let me know if this helps.

Bea

I’ve noticed, at least in ListBox, that setting DisplayMemberPath enables keyboard lookups on the control. So if I start typing the first few letters of an item’s text, the selection jumps to that item.

What’s especially useful is that this behaviour remains even if I also set ItemTemplate, so that my items can take on a customized appearance.

However, I notice that Visual Studio in the background throws a tonne of these silent exceptions:

System.Windows.Data Error: 20 : Both ‘ContentTemplate’ and ‘ContentTemplateSelector’ are set; ‘ContentTemplateSelector’ will be ignored.

Is this ok? Or is there a recommended way to get the keyboard lookup behaviour while using ItemTemplate?

Cheers,
Matt