UIAutomationSpy and VisualUIAVerify are able to inspect the "Default action set window" and can see it's controls etc..
It freezes immediately when doing
$FilterDialog | Get-UiaControl | Read-UiaControlName
$FilterDialog | Get-UiaControl | Read-UiaControlAutomationId
This,however, does work...
$Expressionpanel = $FilterDialog.NavigateToFirstChild().Highlight()
# Doubleclick first filter
$listbox = $Expressionpanel.NavigateToFirstChild().NavigateToFirstChild().NavigatetoNextSibling().NavigateToNextSibling().Highlight()
Another strange behaviour i've noticed is with treeview/treeviewitems...
I have a treeview that looks like:
I can get the nodes perfectly by using
$NavigationTree = $GUIMainForm | Get-UIATree -AutomationId "TreeViewMenu"
$NavigationTree | Get-UiaTreeItem -Name "Dashboard"
$NavigationTree | Get-UiaTreeItem -Name "Collections"
$NavigationTree | Get-UiaTreeItem -Name "Layers"
$NavigationTree | Get-UiaTreeItem -Name "Packages"
But as soon as one of the rootnodes has a childnode,I am no longer able to get treenodes for any of the following rootnodes.
e.g. Dashboard has a childnode, I can get treeitems for Dashboard and it's child, but I can no longer get treeitems for collections, layers or packages
e.g. 2 Collections has a childnode, I can get treeitem for Dashboard,Collections and it's child, but I can no longer get treeitems for layers or packages.
Currenlty i'm working around this by automating bottom to top, first adding all nodes I need to bottom of the tree and then working my way up, but I'm sure i'm going to run into the situation where this workaround will no longer cut it...