I'd love to be able to throw in MSGBOX commands in my script in a nonblocking way so that the script can continue without waiting for user to close the dialog.
Will the /Tn option do what you want ? If not you could open another window (session) to display what you want. Mr. Jiggs yjchung wrote: I'd love to be able to throw in MSGBOX commands in my script in a nonblocking way so that the script can continue without waiting for user to close the dialog.
Or maybe the OSD or SCREEN commands will fit your need... Mr. Jiggs yjchung wrote: I'd love to be able to throw in MSGBOX commands in my script in a nonblocking way so that the script can continue without waiting for user to close the dialog.
What I want to use MSGBOX or something similar is that I have a long script that invokes many processes in steps and I want to be able to pop up a message box if there's something interesting. That way, the user can start the script, walk away, come back many hours later and see that something interesting happened while running the script. OSD doesn't stick around and can't be dismissed by the user. SCREEN isn't useful since the message will be scrolled off. For now, I've echoed these messages in eye catching colors so it can be seen when scrolling back through the buffer but it'd be nice if message boxes can be popped off that doesn't require immediate action from the user before the script can continue.
It seems there are some event plugins that you may be able to use by having a monitor process that pops up messages from a file, or some equivalent mechanism. On Fri, Sep 19, 2008 at 1:56 PM, yjchung <> wrote: -- 2008 Fridays: 4/4, 6/6, 8/8, 10/10, 12/12 and 5/9, 9/5, 7/11, 11/7. Next year they're Saturday. Measure wealth by the things you have for which you would not take money.
How about using the LOG function, or just TEE the relevant commands/actions to a "status files" and, at the start of the script, open another session where you TAIL the log or "status file"... yjchung wrote: What I want to use MSGBOX or something similar is that I have a long script that invokes many processes in steps and I want to be able to pop up a message box if there's something interesting. That way, the user can start the script, walk away, come back many hours later and see that something interesting happened while running the script. OSD doesn't stick around and can't be dismissed by the user. SCREEN isn't useful since the message will be scrolled off. For now, I've echoed these messages in eye catching colors so it can be seen when scrolling back through the buffer but it'd be nice if message boxes can be popped off that doesn't require immediate action from the user before the script can continue.
This is a brute force approach: start tcc /c msgbox ok "Status" my status msg But having a monitor application run would be the better way to go. start tcc /c tail /f monitorfile.txt ... echo My Status Msg >> monitorfile.txt ... echo My 2nd Status Msg >> monitorfile.txt ... echo My 3rd Status Msg >> monitorfile.txt -Scott "Mr. Jiggs" <> wrote on 09/19/2008 05:20:29 PM:
Thanks for all the suggestions.. For now, I've decided to use "start /c /inv msgbox /n /w OK "Title" Message" Each tcc session that gets started eats up some memory but as long as I don't end up with a gazillion messages it's fine.
From: samintz Sent: Friday, September 19, 2008 4:52 PM Subject: RE: [Suggestions-t-465] Re: Unblocking option for MSGBOX? Alternately, DETACH MSGBOX OK "Status" my status msg Jonathan Gilbert
