CODEWITHSUNDEEP
c#wpfxamllistviewdatatemplate
Rich
Rich

Reputation: 87

Find child elements in a WPF ListView ItemTemplate

Given a populated ListView, how do I iterate through each bound template and pluck out the contained ComboBox (or any other control contained in DataTemplate)?

<ListView x:Name="lstCommands">
<ListView.ItemTemplate>
    <DataTemplate>
        <Grid x:Name="gridInputs">
            <Grid.ColumnDefinitions>
                <ColumnDefinition Width="100"/>
                <ColumnDefinition Width="*"/>
            </Grid.ColumnDefinitions>
            <Label Content="{Binding Path=Key}"/>
            <ComboBox x:Name="cbInputCmd" Grid.Column="1" ItemsSource="{Binding Source={StaticResource inputData}}" Tag="{Binding Path=Key}"/>
        </Grid>
    </DataTemplate>
</ListView.ItemTemplate>

Upvotes: 1

Views: 10972

Answers (3)

aex
aex

Reputation: 85

is simple just do this

    <ListViewItem Name="mainiterm" Style="{ StaticResource inboxlst}" Selected="ListViewItem_Selected_1">
            <Canvas Style="{StaticResource inboxcanvas}">
                    <Label Name="namelabel"  Content="lalallala1" Style="{StaticResource inboxlabel1}" />
                <Label  Content="lalallala" Style="{StaticResource inboxlabel2}"/>
              </Canvas>
        </ListViewItem>

and vb

 Dim r = mlistview.Items.GetItemAt(i)
    Dim textYear As Label = Nothing
    Dim s As Canvas = r.Content
    Dim a As Label = s.Children.Item(1)
    a.Content = "Disconnected"

a is a label, s is a cavas

Upvotes: 1

Kent Boogaart
Kent Boogaart

Reputation: 178810

Firstly, avoid doing so unless you really need to. If you absolutely must, you can use DataTemplate.FindName, where the templated parent is the ListViewItem generated by the ListView. To get the ListViewItem, use the ListView's ItemContainerGenerator.

Update: the reason I suggest avoiding this approach wherever possible is because it creates more tightly-coupled, brittle code. The OP didn't mention why he wanted to do what he was asking, but I suspect he could achieve his goal by more idiomatic means, such as with bindings.

Upvotes: 3

Aran Mulholland
Aran Mulholland

Reputation: 23945

you could try using the LogicalTreeHelper or VisualTreeHelper which lets you query an object for its children, but if you were binding your combo boxes to the item your list view is displaying you would not have to worry about 'getting' them at all.

Then you could just look at your item.

Any time you find yourself walking the visual or logical tree looking for elements which exist in your ui, so that you can get their values, ask yourself 'what am i missing here' 'why isnt my business (or view model) being updated with relevant data when the user interacts with the ui?'

For the example above I would build a view model that had two properties, a String (for your label) and a SelectedItem (that you could bind your combo box selected item to). its easier, more robust and it stops you having to trawl through the visual elements. one of the beautiful things about xaml/wpf is that it seperates your logic from your view. what you are suggesting will break this model. You will entangle the view with your logic and from there on it gets messy...

Upvotes: 0

Related Questions