LegacyIAccessiblePattern for DataGrids

[aaron240]

I'm new to github.com and FlaUI. This is not an issue, but just a question. I am trying to obtain the LegacyIAccessible State value for the rows in a DataGridView table in C#.

I was using the UIAComWrapper to retrieve the LegacyIAccessible State value to determine which row was selected. And it worked perfectly, until now. I'm not sure what happened, but it now returns a state value of 0 for all rows while Inspect.exe shows that the value is definitely not zero. According to Inspect, the DGV I'm looking at has no pattern available (nor does not have support for any pattern) except IsLegacyIAccessiblePatternAvailable.

I know this isn't much information, but would FlaUI be a possible solution for me to use to obtain those values accurately and more consistently? If more info is needed, I'll do my best to provide answers. Thanks.

[Roemer]

Hi
First: Is is possible to provide the application you try to test? If not, can you provide some screenshots showing the datagridview / cells in any of the inspect tools?
Thanks

[aaron240]

Attached are the Inspect.exe screenshots for the DGV, it's Rows, and the cells in each row. I've actually coded a work around, although not very efficient. Since only the LegacyAccessible.State value was incorrect, I decided to capture the LegacyAccessible.Value of each row before and after a row is added. Luckily for me, every time a row is added to the DGV, it is automatically selected, so I am able to determine which row is selected simply by comparing the before and after. But I still would like to know why UIAComWrapper reports the State value as 0, and for one or two of the rows are an int value of around 94834 (I think). It has worked perfectly before, and still does for the most part, but it seems to always break at some point during the execution of my code.

[aaron240]

But there's even a bigger problem I'm facing now where I can't even get to an element towards the end of my script. When I keep running FindFirst, it returns null when I know it's loaded on the UI and Inspect can see it. I am able to find the element when I execute that code in the beginning of my script 100% of the time, but after part of my script is executed, it seems to no longer be able find it. And immediately after I stop the debugger, Inspect.exe finds it easily. I've tried UIAutomationClient COM library, UIAComWrapper,
IUIAutomationElementArray array = element.FindAll(UIAutomationClient.TreeScope.TreeScope_Descendants, automation.CreateTrueCondition()),
IUIAutomationElement elementWalker = automation.RawViewWalker.GetFirstChildElement(element);

.NET UIAutomationClient has never been able to see it. But this may be an issue for another time/place.

[aaron240]

I used the UIClientAutomation.dll in the COM library and it seems to work now. I'm not 100% sure if it's because I'm using a different .dll reference now, or if it's because I'm performing the validation of the LegacyIAccessible state in a different class library that I've created.

I only say that because the other problem that I faced, where I couldn't find an automation element via code, but it appeared in Inspect.exe. I'm not sure why, but it seems like it couldn't find it when I performed automation element searches within the same class library. Moving all automation element searches to their own library allowed me to find that specific element.

I did find the article below that seems to make automation elements pretty delicate to use and could cause some problems. For now, I'm just going to use the different class library. If any other difficult problems occur, I'll try executing my searches on different threads.

https://docs.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-threading-issues