issue resolved, had not used ASCII conversation
Runner.CallObjectMethodAsync(Sys.Desktop,"KeyUp",Asc(aqString.ToUpper(sInstructionValue)))
issue resolved, had not used ASCII conversation
Runner.CallObjectMethodAsync(Sys.Desktop,"KeyUp",Asc(aqString.ToUpper(sInstructionValue)))
I have one more question regarding this,
After the following code,
While Not CallResultObj.Completed
aqUtils.Delay 100
WEnd
The "CallResultObj.Completed" is True however, "CallResultObj.ReturnValue" value is blank,
1. so are we sure that TC has completed the operation of "KeyUP" and "KeyDown" ?
2. "CallResultObj.Completed" is True, is it because it has made a successful call to the sub/function ? or is it because it has got a confirmation from the sub/function that it has been called and completed ?
KeyUp and KeyDown don't have a return value. These methods are synchronous, meaning they pause the test until they complete execution. So the code should be:
Call Sys.Desktop.KeyDown(...) Call Sys.Desktop.KeyUp(...)
Could you please clarify what you are trying to do exactly? If you need to input text into an object, you should use the Keys/SetText/wText or similar methods/properties of that specific object. For example:
Call Sys.Process("notepad").Window("Notepad").Window("Edit").SetText("Hello")
You can record your key presses to see which method and syntax to use.
We have one generic/common method, what it does is, press sys.desktop.keydown and keyup to type each character across all kind of text boxes, however we are now facing a situation where type action is not complete and control has already moved on to the next script. Control has moved on because using sys.desktop.keydown/keyup has been a subroutine call without knowing exactly the operation was complete or not.
one such problematic control where typing is an issue is CMD prompt window/DOS window.
If KeyUp and KeyDown methods are synchronous, why is that script execution moves on to next execution set, even before the typing is complete. Also the typing s very slow and takes some time.
The issue is that interaction 2 does not wait for interaction 1 to complete before it begins. Is there any way to acknowledge Interaction1 has been completed ? so that we can move on to next
We cannot use keys/setText because of the restrictions it comes with .i.e simulate keystrokes incorrectly
