10-20-2024, 10:25 PM
The problem with AutoHotKey. It's only a keyboard spewer with no feedback. Need to tweak wait commands for things not keyboard queue-able, especially dealing with drop down windows. So input and output timing can not be controlled. I automate autohotkey commands to send things. But I need to be the commander at the keyboard and select the windows.
Using dos piping (ie: < and >) is only usable until you do it. If I use "ssh" command in a cmd batch, all is well until ssh program executes. Then the batch execution point suspends until I exit ssh. To proceed after the batch ssh command line. So it's good to get me into ssh, but no more automation when it starts.
This was really a PIE-IN-THE-SKY expectation. Thought might be a magician out there who could work there VooDoo.
Using dos piping (ie: < and >) is only usable until you do it. If I use "ssh" command in a cmd batch, all is well until ssh program executes. Then the batch execution point suspends until I exit ssh. To proceed after the batch ssh command line. So it's good to get me into ssh, but no more automation when it starts.
This was really a PIE-IN-THE-SKY expectation. Thought might be a magician out there who could work there VooDoo.