As I say, I've never tested a PowerBuilder application, so these were just suggestions.
But this:
"What Pb is doing is unfortunately not known to me. We replace actual dataobject insinde Datawindow to another almost the same. We dont create publicly a new datawindow"
... especially the part in bold/italic does sound suspiciously like they have created a second instance of something? It might explain your ControlIndex of 2. But then, a cluster of radio buttons could also report a control index this way. I don't know how PowerBuilder radio buttons are presented.
So I guess my suggestion is still a possibility. But it also sounds like your dev team don't really understand the controls they're working with. Which would concern me! ("What Pb is doing is unfortunately not known to me." !!!)
If they are creating duplicate instances, I would normally expect these to be visible to me in the object model. But as they also mentioned they don't create it publicly, so maybe not. Someone who knows PowerBuilder would know better than I do. Normally, I would expect that to be the dev team, but in this case, maybe not ....
You know, actually def care about bugs that can be simulated manually - thats the problem.
If I cant click a object with testcomplete but i can do it manually they don't care.
I have same feelings that "We replace actual dataobject insinde Datawindow to another almost the same" may be a second instance that is not properly recognized by testcomplete.
And about control index - looks like they are just sorted diffrent (shouldnt matter for TC if i click object by fullname):
In these 80% radiobuttion A - has index 1 and B has index 2.
In these 20% radiobutton A - has index 2 and B has index 1.
Question is: why just some fields are invisible for TestComplete if they replace a whole dataobject?
Problem is with radiobuttions/combobox, normal text fields are fine.
If noone here will have some knowledge about this case in PB and TC then ill ask dev to make a version just for me without that dataobject repleace.
