Forum Discussion

ast's avatar
ast
Contributor
8 years ago

Powerbuilder DataWindow: Where are Fields, Events, specific functions ?

Hi there - How can i make Fields and Events visible for enhanced testing (see attachment)? - In general: Where can I find specific developers functions on a Powerbuilder object? Thanx
Colin_McCrae's avatar
Colin_McCrae
Community Hero

I interpreted "specific developers functions" as meaning native properties and methods?

 

But I'm not a PowerBuilder guy. That's just my interpretation.

ast's avatar
ast
Contributor
8 years ago

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.

  • tristaanogre's avatar
    tristaanogre
    Esteemed Contributor
    8 years ago

    "

    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.

    • ast's avatar
      ast
      Contributor
      8 years ago

      Hi

      Thanks again for your help!

       

      - MSAA settings for the specific project: check
      - Actual (newest) build with accessible properties: check

       

      I've many projects, so I've removed the pbdw*125 in the current project text recognition properties and restarted TestComplete: I'm afraid nothing changed...

      • tristaanogre's avatar
        tristaanogre
        Esteemed Contributor
        8 years ago

        Can you verify that you don't have your process actually in the Extended Support portion of Text Recognition? Removing the components won't do much if the entire application has Text Recognition applied.

        If that doesn't work...  not entirely sure what to tell you. I've hit my limit of ideas for the moment... perhaps a brainstorm will come to me but this is the point where I would open a ticket to SmartBear Support.

         

        https://support.smartbear.com/message/?prod=TestComplete