Glenn Posts: 99 06/10/2015	Glenn Posts: 99 Seems that the "start" command is supported, but doesn't get the asynhcronous behaviour of the "start" command in CMD.exe. Generally, the purpose of "start" is to launch a program and _not_ wait for it to complete, but continue with the next operation.... unless the /WAIT option is given. Along with that, the nice "CMD-like" window that displays while the WinCommand is running is great for debugging, but it would be nice to have a checkbox to make it auto-close when complete. Or just to make it always auto-close when complete, but the user can add a pause command if they want it to stay around for debugging.
	link
Gianluca Administrator Posts: 1274 13/10/2015	Gianluca Administrator Posts: 1274 I have a different idea. The SyMenu cmd-like window will become optional in one of the next version because it creates more errors and strange behaviours than I ever imagine. So you have a check to enable the cmd output and another radio button to choose among the standard cmd window or the cmd-like SyMenu window. I know that this sentence doesn't reply to your question but I'm simply saying that in future any bug on the SyMenu cmd windows could be solve using the Windows standard one.
	link
Glenn Posts: 99 17/11/2015	Glenn Posts: 99 The use of the system CMD window may indeed resolve such problems. IIRC, I resolved my issue by writing a little AutoHotKey script to do the asynchronous part. AutoHotKey fits well with SyMenu: although its syntax is atrocious, it is small, portable, and quite capable.
	link

---