"The window does not repond" problem
I'm trying to set the text value of a combo box (standard window for choosing path to file in Windows 7) using given string in my test. I'm using such line: Call Sys.Process("AdaptiveVisionStudio"...
Forum Discussion
Hi ,
Did you try "Keys" method to insert text into the TextBox ?
Note:
I have noticed one difference between "SetText" and "Keys", the "Keys" method is much much slower than "SetText".
Did you try "Keys" method to insert text into the TextBox ?
Note:
I have noticed one difference between "SetText" and "Keys", the "Keys" method is much much slower than "SetText".
Did You try .SetFocus before using .SetText?
I never use setText. I always want to replicate what a user can do so I always use .keys.
This is a massive project that has been running successfully for more than a year.
The only reason to use .keys rather than .settext is if the data entry field has events associated with it corresponding to actually using the keyboard. Otherwise, the general effect is the same and there is VERY little difference.
That said, auto-wait time outs are usually good so long as there is a good stability in the system. However, one thing I know about Windows 10 is that there is a LOT of background processing that goes on that can slow down a machine, some of the latest updates of Win10 especially. So, it's all together possible that your test machine is being taxed.
Something you can do instead of Auto-Wait is start going through and replacing some of the problematic object calls with the approprate "WaitNNN" methods. There may be some objects that simply take longer on Windows 10 to respond properly.
