Forum Discussion
What happens if you change "Keys" to "SetText"? Unless you actually need to simulate keyboard events against the control, SetText will work just fine for entering values into an edit field. I know this doesn't exactly resolve your problem, but it is a work around.
Additional question: Your application under test, is it a 32-bit app or a 64-bit app? It's possible that there may be a bit of a performance problem for TC x64 to send key commands to a 32-bit control. In any case, try SetText... and I would also suggesting opening a support ticket directly to SmartBear customer service as they will be able to help more with technical issues in the tool.
- SanderK8 years agoOccasional Contributor
The reason I use Keys instead of SetText is because this type of edit component does not appear to have that function available.
Our application under test is indeed a 32 bit app, so that might be part of the problem as you say. For now I'll just stick with the 32 bit version of TC, but I thought it would be useful to report this issue.
- tristaanogre8 years agoEsteemed Contributor
Use https://support.smartbear.com/message/?prod=TestComplete to report this issue directly to SmartBear. While smartbear employees to monitor these forums and respond here, this kind of issue would do better as something to send directly to them.
Related Content
- 8 years ago
- 11 years ago
- 7 years ago
Recent Discussions
- 5 days ago
- 5 days ago