| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 32.1 | READ.ME for SAY | UHUH::BEERMAN | Charlie Beerman | Tue Jan 04 1994 11:37 | 37 |
| 32.2 | SAY.TXT | UHUH::BEERMAN | Charlie Beerman | Tue Jan 04 1994 11:39 | 66 |
| 32.3 | New version, new filename | UHUH::BEERMAN | Charlie Beerman | Thu Jan 13 1994 11:08 | 36 |
| 32.4 | Problems finishing a thought... | ICELAN::AARON | Aaron Sakovich, Support Consultant | Fri Apr 01 1994 02:17 | 14 |
| 32.5 | Bug in DECTALK.DLL | UHUH::BEERMAN | Charlie Beerman | Fri Apr 01 1994 11:57 | 24 |
| 32.6 | SAY102 | UHUH::BEERMAN | Charlie Beerman | Sat May 07 1994 02:39 | 13 |
| 32.7 | Problem fixed | BGSDEV::HALLAHAN | | Wed Aug 17 1994 14:08 | 5 |
| 32.8 | 'SAY' as a background process? | AWECIM::LUPISELLA | | Tue May 06 1997 23:50 | 23 |
| I am running 'say' by invoking it from within a Visual Basic
Application. The Application is an Event Reporting System. I am using
'say' to tell me when a particular event has occurred as opposed to
watching the viewer all day. The problem I am having is that when my
event occurs, whatever Window I have activated at the time, becomes
automatically deactivated while the 'say' process runs. I have to keep
reactivating an edit session or WEB browser session or whatever
everytime an event occurs.The active window is automatcially changed
to an MS DOS window which comes up at the time of the event. Is there
any parameter that I can pass to the 'say' command line which will tell
it to run as a background proces? I am running in a WIndows NT V3.51
environment. The command line I am using from within my application:
say -d c:\DECTALK\DIC\USER.dic [:punct none][:ra 200][:nh] $MESSAGE
($MESSAGE is interpreted by the Visual Basic Application then spoken by
'say')
Thanks in Advance
Jeff Lupisella
Digital SemiConductor
Hudson, MA
|
| 32.9 | might be a generic Windows or NT question.. | TEKVAX::KOPEC | Tom Kopec W1PF | Wed May 07 1997 15:46 | 16 |
| Hm. Because it runs as a dos program (I think; I don't use it much),
maybe you can twiddle the PIF for it and then "run" the PIF.. or maybe
VB has some option to run a DOS command without a box..
Here's the "official" response.. (I'm just the messenger..)
>Hi Tom;
>
>Thanks for sending this to me. However, say is a sample program. If the
>user wants to do something different then what the sample code does, the
>user can change it. If the issue is that the sample code is not
>supplied, is incomplete, etc., then I agree we need to address it.
>
>Regards,
>
>Carl
|
| 32.10 | Closing the command prompt window | BGSDEV::HALLAHAN | | Mon Jun 02 1997 18:47 | 51 |
|
I don't know how to prevent the command prompt
(MSDOS) window from becoming the foreground window,
but I do know how to make it close when speaking has
completed. This will cause the previous foreground
window to regain focus. Instead of launching say.exe,
launch cmd.exe. Since I don't have Visual Basic, I
cannot ensure the exact sequence. I tested this by
launching say from another command prompt window.
Here's what I did:
start cmd /C say <string>
where <string> is your composed string. The /C causes
the command prompt window to close when say is
complete. I would appreciate it if you would post
a reply that indicates if and how this works.
Note that typing:
cmd /?
will give all of the switches for cmd.exe.
Bill Hallahan
hallahan@zko.dec.com
|