Forum Discussion

shenyusun's avatar
shenyusun
Contributor
9 years ago

Unable to get the object when the software is in (Not Responding) state

Hello beautiful people,   I am running to an issue that I am unable to get the 'Yes' button with the software that I am testing.   Basically, when I click a certain button in the current software...
  • bbi's avatar
    bbi
    9 years ago

    About keys not working, don't use the testobject Keys but use the LLPlayer instead of.

     

    This insert a WM_Key message directly in windows loop and thus by-pass any code restriction 

     

    So to send a real ENTER key press to system ;

     

    LLPlayer.KeyDown(VK_RETURN, 5);
LLPlayer.KeyUp(VK_RETURN, 5);

    First parameter is virtual key code, list of them is here.

    Second optional parameter is delay, better to use it to simulate real-life press which is not INSTANT.

     

    BTW you can use the same for mouse message, so a left click is:

     

    LLPlayer.MouseDown(MK_LBUTTON, xcoord, ycoord, 25);
LLPlayer.MouseUp(MK_LBUTTON, xcoord, ycoord, 25);

    First parameter is the mouse button.

    Second and third parameters are coordinates.

    Fourth parameter is delay, better to use it to simulate real-life press which is not INSTANT.

     

    Be careful, the mouse or keyboard event is sent to the system and thus is treated by the currently active windows.

     

    For a clik or a press, you need always to do both actions, down and up 

     

    For more information, search for LLPlayer in TC help.

     

    Hope it helps.

     

shenyusun's avatar
shenyusun
Contributor

Thanks bbi,

 

It's a standard modal dialog.

 

The shortcut key did not work because it require testObject.Keys

 

TC could not get the modal window object somehow.

 

When I manually press 'y' , the window took it, but when I tried to make TC to do it, it could not find the object.

bbi's avatar
bbi
Contributor
9 years ago

About keys not working, don't use the testobject Keys but use the LLPlayer instead of.

 

This insert a WM_Key message directly in windows loop and thus by-pass any code restriction 

 

So to send a real ENTER key press to system ;

 

LLPlayer.KeyDown(VK_RETURN, 5);
LLPlayer.KeyUp(VK_RETURN, 5);

First parameter is virtual key code, list of them is here.

Second optional parameter is delay, better to use it to simulate real-life press which is not INSTANT.

 

BTW you can use the same for mouse message, so a left click is:

 

LLPlayer.MouseDown(MK_LBUTTON, xcoord, ycoord, 25);
LLPlayer.MouseUp(MK_LBUTTON, xcoord, ycoord, 25);

First parameter is the mouse button.

Second and third parameters are coordinates.

Fourth parameter is delay, better to use it to simulate real-life press which is not INSTANT.

 

Be careful, the mouse or keyboard event is sent to the system and thus is treated by the currently active windows.

 

For a clik or a press, you need always to do both actions, down and up 

 

For more information, search for LLPlayer in TC help.

 

Hope it helps.

 

  • shenyusun's avatar
    shenyusun
    Contributor
    9 years ago

    Thank you so much bbi!!

     

    This worked for me!! It is risky, but it's a great workaround for me since this problem has blocked me for days.

     

    This is very useful when the program became not responding state.

  • sanjay0288's avatar
    sanjay0288
    Frequent Contributor
    9 years ago

    Hi,

       In addition to bbi response If  you want to use the Runner.CallObjectMethodAsync. You also need to call the method which invokes the modal dialog asynchronously.

    Below is the sample vbscript code on handling modal dialog

     

     Set ResObject = Runner.CallObjectMethodAsync(GridObj.ActiveRow.Cells.Item(2), "HideDropDown")  ‘ This is the method which invokes the modal dialog. Hence this also needs to be an asynchronous call 

        Set p = Sys.Process(<process name>)
        Set w =p.Window("#32770", "Configuration", 1)
        Set w1 = w.Window("Button", "&Yes", 1)
    Set ModalDialogObject = Runner.CallObjectMethodAsync(w1 , "ClickButton")
      ModalDialogObject.WaitForCompletion 2000
       If ModalDialogObject.Completed = True Then
        Log.Message "Success"
      Else
        Log.Message "Failure"
      End If