Hi,

Thanks for the suggestion. The video was very helpful.

I am able to dig through the child elements and identify the buttons and their properties.

set grid=WpfWindow("Home").XamDataGrid("Grid")
intButCount=grid.GetSubItemProperty(gridCell,"{0}[0]","FWElement.Children[0].Children[3].Children[0].Children[0].ChildCount)

for j=0 to intButCount-1
strActualButtonName=grid.GetSubItemProperty(gridCell,"{0}[0]","FWElement.Children[0].Children[3].Children[0].Children[0].Children["&j&"].Name")
blnEnable=grid.GetSubItemProperty(gridCell,"{0}[0]","FWElement.Children[0].Children[3].Children[0].Children[0].Children["&j&"].IsEnabled")
msgbox strActualButtonName & "--" & blnEnable
next

I have taken the child elements of the parent node (Contentvalue presenter) and its children (and inturn its children) to identify the stack panel.

From the snoop, object hierachy of the object is identified as:

<<Cellvaluepresenter>>.<<DockPanel>.<<Content Control -3rd child>>.<<ContentPresenter>>.<<Stack Panel>>
ie: FWElement.Children[0].Children[3].Children[0].Children[0]

If there is a change in this object hierarchy then the above object identification will fail.

Instead, do we have any option to identify the child elements with some unique identification properties, for ex:I have to identify the content presenter inside FWElement??

Is there any other way to over come this issue??

Please suggest.

Thanks,
Dhivya.D

Hi Dhivya, 
   There is something to be said that if the object hierarchy changes significantly the test should fail. But there are ways around it. You can build a loop that finds a child element by any property or type you want as you have access to all the properties, and the Type names via Type.FullName or Type.Name. So you can do something like the following, this assumes that I am searching a Cell of XamDataGrid for a child element of Type Button with a Background color of red. You can of course modify it as you need. This may take a bit to run, you can speed it up by passing in a longer rootPath then just FWElement. Of course as long as you know your CellTemplate isn't going to change or if it does, that is a bug in the test that you know you will need to correct you can just hard code the path.

Set oGrid = WpfWindow("MainWindow").XamDataGrid("xdg")

msgbox FindChildByTypeAndColor(oGrid, "{0}[Label]", "FWElement", "Button", "#FFFF0000")

Function FindChildByTypeAndColor(grid, cellID, rootPath, typeCheck, colorCheck)
    NOTFound = ""
    
    ' Get the current FrameworkElement Type
    typeCrnt = grid.GetSubItemProperty(gridCell, cellID, rootPath & ".Type.Name")
    
    If typeCrnt = typeCheck Then
        ' If the type is what we were looking for lets check the other propert(y/ies)
        colorCrnt = grid.GetSubItemProperty(gridCell, cellID, rootPath & ".Background.ToString")
        
        If colorCrnt = colorCheck Then ' If we matched all the properties we were looking for then return the rootPath
            FindChildByTypeAndColor = rootPath
            Exit Function '
        End If
    End If
    
    ' If we didn't find it, lets see how many children this has
    childCount = grid.GetSubItemProperty(gridCell, cellID, rootPath & ".ChildCount")
    
    If childCount = 0 Then ' No children, then we are on the wrong visual tree node, return back up
        FindChildByTypeAndColor = NOTFound
        Exit Function
    End If
    
    For i = 0 To childCount - 1
        FindChildByTypeAndColor = FindChildByTypeAndColor(grid, cellID, rootPath & ".Children[" & CSTR(i) & "]", typeCheck, colorCheck)
        If FindChildByTypeAndColor <> NOTFound Then ' If the value was found in this call pass it back up to the previous call
            Exit Function
        End If
    Next    
    
    'If it hits here, it means it looped through all its children and didn't find it, set it to empty and pass it to the previous call
    FindChildByTypeAndColor = NOTFound
    Exit Function
End Function

Hope this helps,

I'm trying to do something similar to what is being done in this post, but infragistics is throwing an error telling me that "[Children] is not an indexed property"

Could someone tell me why that is?...

I need to get the text embedded in button that is embedded in the xamdatagrid cell so that I know what cell/button to click.

I tried the exact code given and it popped the same error

Hi Joseph,

I have arrived at the above mentioned code by identifying the exact object hierarchy using Snoop tool. So try to spy your AUT objects using Snoop and come up with FWelement code according your object hierarchy.

Thanks,

Dhivya.D

I tried using the hierarchy/snoop to figure out the chain of children to go through to get the stuff i'm looking for.

However, my problem is that when i put an index on FW.Children (e.g. FW.Children[0] as opposed to FW.Children) the add-in spits out an error telling me that it's not supposed to be indexed and when I don't index and print out getSubItemProperty(... , ... , "FWElement.Children.Type.Name") it prints out "DependencyObject[]" or something

Bear in mind I am brand new to this add-in, so this post is acting as sort of training wheels - the whole FWElement thing seems quirky to me

Essentially I'm just toying with it to understand how it works and what attributes etc are available and as I mentioned, I tried using the function you built in your previous post.

lines as simple as this  fail with the error talking about how that attribute isn't supposed to be indexed:

msgbox  wpfwindow("window").XamDataGrid("grid").GetSubItemProperty( gridCell,"{1}[File Number]", "FWElement.Children[0].ChildCount" )

I'll give the webinar a look to see what I can learn from it, but i have a hunch that line of code isn't supposed to be popping errors