> I don't see a need for IDE to keep giving itself focus when running to
> end or breakpoint.
I apparently haven't explained the IDE behavior clearly. To recap:
* The IDE runs scripts itself; there is no external app (such as TCC.EXE)
involved.
* The IDE is not switching focus between itself and another app; it is
(normally only rarely) switching focus between its own two windows.
* The IDE is not switching focus between its own two windows on every
command; it only does it when it detects that you're running a command that
requires keyboard input (like INKEY or INPUT).
* This is a *good* thing, as it normally leaves the user in the debugger
window, where they have immediate access to all of the debugging tools.
* This works well in 99.9999% of all cases; the only one where it creates
a potential problem is in your (slightly demented) example of putting an
INKEY /W0 inside an infinite loop, and then telling the debugger to run (and
not debug) the script. (The IDE detects the INKEY, switches to the console
window, immediately times out, switches back to the debugger window, ad
infinitum.)
I do NOT feel that it's a good idea to force the user to manually switch
between windows for the 99.9999% of batch files that do not suffer from this
issue, and I have no intention of changing the current behavior for v12.
Rex Conn
JP Software