Dear folks,
I was wondering if it possible to change or completely disable the global hotkeys?
Currently I am running a console application on a remote machine, where it watches and only seldomly does tasks - but the machine is in use by some human at the same time.
Therefore it happens, that the human hits the <End> button e.g. while renaming something in Windows Explorer which then does not work and also pauses the test execution.
Best would be to change this to something else (e.g. Ctrl+End or similar) or to disable hotkeys completely.
I searched Ranorex settings, Solution properties, Test Suite properties but did not find any useful section.
Any ideas?
thanks!
Disable or change hotkeys?
Re: Disable or change hotkeys?
Hi,
You can define the abort key via this line placed in program.cs (before initializing test). Simply change Pause with whatever you prefer.
Ideally, the machine should not be used by anyone else during the test run! I would even recommend to disable mouse and keys input, via these lines (and re-enable them at the end of test)...
You can define the abort key via this line placed in program.cs (before initializing test). Simply change Pause with whatever you prefer.
Code: Select all
Keyboard.AbortKey = System.Windows.Forms.Keys.Pause;
Code: Select all
Mouse.Enabled = false;
Keyboard.Enabled = false;
Pavel Kudrys
Ranorex explorer at Descartes Systems
Please add these details to your questions:
Ranorex explorer at Descartes Systems
Please add these details to your questions:
- Ranorex Snapshot. Learn how to create one >here<
- Ranorex xPath of problematic element(s)
- Ranorex version
- OS version
- HW configuration
Re: Disable or change hotkeys?
Oooo, that's a great tip! That helps me out here too. Thanks for that one.
Re: Disable or change hotkeys?
Hey, ahh thats nice, thanks.
In this case it is no real test, it is just a small watcher script that watches a certain browser tab and clicks once after 30 mins and then again after ~60mins, so the machine is almost free in between.
I know it is not ideal, but setting up a fresh machine for doing 1 click per hour also doesn't seem good.
Yes, ideally.
In this case it is no real test, it is just a small watcher script that watches a certain browser tab and clicks once after 30 mins and then again after ~60mins, so the machine is almost free in between.
I know it is not ideal, but setting up a fresh machine for doing 1 click per hour also doesn't seem good.