The topic you reference in your screenshot actually describes a number of things that need to be done in order to properly expose properties and such of a PowerBuilder application. It describes the need to make sure you add your control to the MSAA options for your project, configuring the component in PowerBuilder to have an AccessibleName property defined for each component that you are adding to MSAA, etc. Also, note, that the topic you referenced (https://support.smartbear.com/testcomplete/docs/app-testing/desktop/power-builder/classic.html) is for PowerBuilder Classic for a specific version set of PowerBuilder.
If you follow all those steps, both in TestComplete AND in your actual application (note that this requires you to ask your developers to make some changes to the components), and you still have the problem, let us know and we'll figure something else out. But it looks to me like, at this moment, you're missing some of the necessary configuration and, therefore, don't have that stuff exposed.
As for your second question... I'm not familiar with Powerbuilder to that level so I'm not sure I understand the question. What do you mean "specific developers functions"? If you are talking about the code behind the form that is not directly connected to the UI, then there isn't a way of doing so that I know of.
I interpreted "specific developers functions" as meaning native properties and methods?
But I'm not a PowerBuilder guy. That's just my interpretation.
Hi there
Thanks for your information.
Colin_McCrae: Yes, right interpretation :-). I mean native properties and methods.
I think I've everything configured:
- Show hidden members: enabled (see attachment above)
- Powerbuilder Data Window: enabled in MSAA (see attachment above)
- Accessible properties are set to the table/data window I want to test (but not for each table/data window - there are many others. Could be this the problem?)
- We're using PowerBuilder Classic version 12.5.2.5550
tristaanogre: What changes to the components do you mean? Are there more than AccessibleName, AccessibleDescription and AccessibleRole?
Thanks for further suggestions.
"
I think I've everything configured:
- Show hidden members: enabled (see attachment above)
- Powerbuilder Data Window: enabled in MSAA (see attachment above)
- Accessible properties are set to the table/data window I want to test (but not for each table/data window - there are many others. Could be this the problem?)
- We're using PowerBuilder Classic version 12.5.2.5550"
Couple of things here. First of all, verify that the MSAA settings are made on your specific project and not on the Default Project Properties. An easy mistake to make (I've done it often) which is why I suggest it. Secondly, make sure that you have an actual build of your application with those accessible properties configured. Again, easy mistake to make to drop in the wrong build.... done it many times with the debugger version of a Delphi app I used to test.
As for the component changes... yeah, just the accessibility things.
Something else I'm seeing, though... and I wonder if this might be what's happening. Looking at your screenshot, you have a bunch of the child objects showing up as "TextObject". This looks like you have the pbdw* components also configured under TextRecognition (Project Properties -> Open Applications -> Text Recognition). I'm wondering if, for some reason, this configuration combination of the same component type being accessed through two different Open Application methods is confusing things. Go into the Text Recognition section and, if it's there under either accepted windows or if your application is listed under Extended support, try removing it and see if that corrects things.
