Well, that does work but as vefatica points out, that affects every instance.Options / Configure Take Command / Windows / Startup Mode.
My apologies. I didn't realize there were different startup settings for TCC and TCMD.Options / Configure Take Command / Windows / Startup Mode.
This is not the case when calling TCC from an external app that I'm guessing applies its own control over the TCC window size. I use an old scheduler http://[URL="www.cypressnet.com/Products/Launchpd/download.htm"]www.cypressnet.com/Products/Launchpd/download.htm[/URL] to launch several TCC jobs, with the window either minimized or invisible, there is no flicker.One thought. There is an initial flicker before the window is minimized.
I noticed that last night. I use http://www.coretechnologies.com/ to manage some tasks and when it invokes TCC it appears on the task bar first - not on the screen immediately followed by a minimize, so no flicker when TCC is dispatched from there.This is not the case when calling TCC from an external app that I'm guessing applies its own control over the TCC window size. --
Works fine here (13.0.14).> I don't get it. TCMD **can** start minimized, either by default, or with
> on its command line. Why can't it honor the nCmdShow arg to
> WinMain, provided by a shortcut, by "START /MIN", or by any
> manner of starting an app?
That works.What works fine? "//WindowState=Minimize" on TCMD's command line works.
That works too.But if TCMD is confugured to start normally, then neither a shortcut with "Run: Minimized"
That also works.nor "START /MIN d:\tc13\tcmd.exe" cause it to start minimized.
TCC has no control over how it's launched. Nor does it have any control> Now if Rex can just eliminate the flicker/distraction of the tcc window
> briefly appearing when Task Scheduler launches it. Should be doable
> as programs other than Task Scheduler are able to launch tcc in a
> minimized state.