Declined New command or new ACTIVATE option request

May 20, 2008
3,515
4
Elkridge, MD, USA
When a batch file needs to send keystrokes to a window, the only method
now available is to use the ACTIVATE command, followed by the KEYSTACK
command. However, if the batch file is executed by a background process, it
is very easy for a different window to be activated from the desktop, or by
another process, before KEYSTACK can deliver the keystrokes. To eliminate
this problem, I'd like to have available a single command that can both
ACTIVATE and deliver keystrokes. Whether this is a new command, or a new
option for the existing ACTIVATE command is irrelevant.
IIRC I had previously requested this feature, for like reasons.
--
Steve
 

rconn

Administrator
Staff member
May 14, 2008
12,365
150
> When a batch file needs to send keystrokes to a window, the only method
> now available is to use the ACTIVATE command, followed by the KEYSTACK
> command. However, if the batch file is executed by a background
> process, it is very easy for a different window to be activated from
> the desktop, or by another process, before KEYSTACK can deliver the
> keystrokes. To eliminate this problem, I'd like to have available a
> single command that can both ACTIVATE and deliver keystrokes. Whether
> this is a new command, or a new
> option for the existing ACTIVATE command is irrelevant.
> IIRC I had previously requested this feature, for like reasons.

Why do you think the behavior would be any different if it was one command
instead of two?

Rex Conn
JP Software
 
May 20, 2008
3,515
4
Elkridge, MD, USA
| ---Quote---
|| When a batch file needs to send keystrokes to a window, the only
|| method now available is to use the ACTIVATE command, followed by
|| the KEYSTACK command. However, if the batch file is executed by a
|| background process, it is very easy for a different window to be
|| activated from the desktop, or by another process, before KEYSTACK
|| can deliver the keystrokes. To eliminate this problem, I'd like to
|| have available a single command that can both ACTIVATE and deliver
|| keystrokes. Whether this is a new command, or a new
|| option for the existing ACTIVATE command is irrelevant.
|| IIRC I had previously requested this feature, for like reasons.
| ---End Quote---
| Why do you think the behavior would be any different if it was one
| command instead of two?

If the two tasks can be done in a single API call, definitely no opportunity
would arise to steal focus. Even if separate API calls are required, the
considerably less time between them would still reduce the probability that
the focus would be stolen.
--
Steve
 

rconn

Administrator
Staff member
May 14, 2008
12,365
150
> | ---Quote---
> || When a batch file needs to send keystrokes to a window, the only
> || method now available is to use the ACTIVATE command, followed by
> || the KEYSTACK command. However, if the batch file is executed by a
> || background process, it is very easy for a different window to be
> || activated from the desktop, or by another process, before KEYSTACK
> || can deliver the keystrokes. To eliminate this problem, I'd like to
> || have available a single command that can both ACTIVATE and deliver
> || keystrokes. Whether this is a new command, or a new
> || option for the existing ACTIVATE command is irrelevant.
> || IIRC I had previously requested this feature, for like reasons.
> | ---End Quote---
> | Why do you think the behavior would be any different if it was one
> | command instead of two?
>
> If the two tasks can be done in a single API call, definitely no
> opportunity would arise to steal focus.

True, but for the lamentable fact that there is no API call to do that.
More like 50+ API calls, and there wouldn't be any measurable difference in
the time between them if it were one command versus two commands. And
KEYSTACK has to wait between each keystroke for the console to signal that
it's ready for another key, which is going to be 99% of the time spent.


> Even if separate API calls are required, the considerably less time
> between them would still reduce the probability that the focus would
> be stolen.

Nope -- see above.

Rex Conn
JP Software
 
Similar threads
Thread starter Title Forum Replies Date
Joe Caverly Done Specify which LIBRARY to run command from Suggestions 2
vefatica File name completion at the beginning of the command line Suggestions 6
L Done Suggestion for TCC 'ver' command Suggestions 8
JohnQSmith Done Modified last command prompt duration Suggestions 5
C Feature Request: Gain some elements of the XXCOPY feature set in COPY or a new "Mass-Copy" command Suggestions 0
D Done SHORTCUT command should accept unexpanded environment variables. Suggestions 0
mfarah Unix-like clear screen keystroke command. Suggestions 0
C Powershell ISE tabbed within Take Command Suggestions 0
D Command Input Feature Request Suggestions 0
R Done Putting command output into an array Suggestions 2
R Done Execute command while at a breakpoint Suggestions 4
R Done Allow single stepping within a command group Suggestions 5
R Declined wish-list: add a command to copy a file to clipboard. Suggestions 17
A Declined Navigation in Take Command Suggestions 4
x13 SORTARRAY command Suggestions 1
R ffind /= and command line Suggestions 0
A Declined Enhance OPTION command functionality Suggestions 2
R Done Command History Window: select more than one line. Suggestions 0
R Declined History: show in which directory a command has been typed. Suggestions 6
N Declined GUI for select command Suggestions 0
Charles Dye Done TCEDIT: Command-line option to print files Suggestions 2
Charles Dye Declined Windows functions and command: Add syntax to specify HWND directly Suggestions 0
vefatica Declined @@key alias at beginning of partial command line Suggestions 10
R Save and load a command dialog set and name it Suggestions 3
Alpengreis Done Add "Slow copy" (/WAIT) parameter to SYNC command Suggestions 1
L Completing the UnQLite command's option set Suggestions 0
joltcoder Done Support an "up" command to go to parent directory and "up3" to go up 3 directories, etc. Suggestions 4
M Declined Command line support for Virustotal Suggestions 0
A Declined Take Command/Debugger as a Visual Studio 2017 add-in/extension Suggestions 4
Joe Caverly Done UnLIBRARY command Suggestions 9
jaejunks Done Option for case-sensitive string comparison in IF command (for CMD compatibility) Suggestions 1
rps Done Log entry command Suggestions 3
rps Done Command and directory history pop-up additions Suggestions 2
rps Command History window options Suggestions 0
rps Declined Command output spacing options Suggestions 0
rps Done Command History edit additions Suggestions 0
J Done Set font in Take Command tabs in a .btm Suggestions 1
rconn Add a parameter to dir command to handle zip files as folders Suggestions 1
rconn Command Line constructor custom DIALOGs for batch files Suggestions 0
rconn A Command-line comparison Suggestions 0
rconn Done database access from command line Suggestions 0
W Done Add colorize to tree command? Suggestions 0
S Done Eject removable USB drives command Suggestions 2
Alpengreis Declined Any chance for quick help with all command-options? Suggestions 3
ehab aboudaya Done Shortcut Key to switch between current active tab & command input Suggestions 0
M Done Start command issue... Suggestions 6
mfarah Done Proposal: new PROMPT $i special command. Suggestions 2
S Done Enhanced TYPE command Suggestions 9
C Done DIFF command Suggestions 0
J Done program elevation from command line Suggestions 0

Similar threads