Hey Robert, thank you for your help, you helped me to figure it out. The WaitAliasChild function was not used properly...
You can see the right script attached.
Thank you again,
Mehdi
The window may be the same window... but there are, technically, two different buttons, one that is "Yes", one that is "OK". The problem is not that it's having problem identifying the window but problem identifying the button. You can handle this two ways.
1) Map both buttons so that your window has "buttonOK" and "buttonYes". Then, in your code, you click on which ever button is necessary at that point in the code.
2) Map the button with Conditional Mapping (https://support.smartbear.com/testcomplete/docs/testing-with/object-identification/name-mapping/managing/modifying/conditional-mapping-criteria.html) where you map the button to be the button you're looking for if it is "Yes" OR "Ok".
hi Robert,
For the first point I already done that, see attached picture please.
So, basically, when you run your automation, you need to specify which button to click. If you attempt to click "Yes" and the "OK" button is what is displayed, then you'll get the message that you saw in the test log because TestComplete says, "I couldn't find the one you said should be there, but I found one similar." It means that your code doesn't match the application behavior. So, the correction to your problem in your OP is to change your code from
TMessage2.Yes.ClickButton
to
TMessage2.OK.ClickButton
Hey Robert,
Thank you for your time,
The matter is that what's I'am already doing :
see the script in the attached pict please...
