I have a form which contains an UltraGrid. I am trying to set a column of this grid to use the ControlContainerEditor like this:
"myGrid.DisplayLayout.Bands[0].Columns[2].Editor = new ControlContainerEditor();"
As soon as I set to use this Editor all the cells of this column become inaccessible to UI Automation tool "Inspect.exe". So, when I hover over them I cannot get any accessibility data from them and consequently I cannot get or set the value of these cells through Coded UI Tests.The exact error message that the "Inspect.exe" UI Automation tool provides is the following:
Cannot get object from point:[Error: FromPoint: hr=0x80004003 - Invalid pointer]You can see this error in the picture attached.It is also notable that as soon as I manually click in one of those cells so that they enter edit mode, this error goes away and then I am able to get their accessibility info. So, this issue arises only when I hover over these cells. In the case of cells that are not editable, there is no way you can access them through UI Automation.This is a huge issue for me because I cannot run Coded UI Tests that manipulate the data of these cells, because the only way I can get their accessibility data is to click on them manually(for the case of cells that are editable).Moreover, I think that in the following link the 1st issue shown might be the one that I am trying to explain:
The problem with this is that I cannot understand the workaround provided in the link, because it seems a little vague.
Could you please tell me the reason why this error arises? Is there any workaround? Note that I am running Infragistics v14.1 in my machine.
Hi Isaak,
I tried this out with a small sample project I whipped up and I am getting the same results.
I have asked our engineering staff to examine this further. To ensure that it will receive attention, I have logged this behavior in our internal tracking system with a Development ID of 237706. The next step will be for a developer to review my investigation and confirm my findings or to offer a fix, or other resolution.
I will leave this case open and update you with any new information after the review. You can also continue to send updates to this case at any time.
You can view the status of the development issue connected to this case by selecting the "Development Issues" tab when viewing this case on the web site.
Please let me know if you need more information.
Hello Mike,Thank you for your prompt reply. I'm glad that you could easily replicate this issue.Looking forward for an update. In the meantime I will provide info about whatever comes up.
Hello Mike,
is there any estimation that you could provide regarding this issue? In the meantime, could you think of any workaround to bypass this issue?Last but not least, I tried to find the "Development Issues" tab that you mentioned in your comment, but I didn't manage to do so. Thank you in advance.
Isaak said:is there any estimation that you could provide regarding this issue? In the meantime, could you think of any workaround to bypass this issue?
It looks like the developers have looked into the issue and fixed it internally. The fix is currently awaiting testing by our quality engineers.
So the fix should be available in the next service release. Checking the service release schedule, it looks like the next one is due to be released on September 15th. If you need a build sooner than that, I can see about getting you an untested build.
I don't believe there is any reasonable workaround.
Isaak said:Last but not least, I tried to find the "Development Issues" tab that you mentioned in your comment, but I didn't manage to do so.
Sorry, I think that might have been a problem on our end. I forgot to make your case publicly visible to you. Please try again and let me know if you still can't see it.
I would really appreciate it if you could provide an untested build because time is of the essence. Moreover I will provide feedback to you as soon as I apply the build on my side.Thank you in advance.