| Title: | DECWINDOWS 26-JAN-89 to 29-NOV-90 |
| Notice: | See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit |
| Moderator: | STAR::VATNE |
| Created: | Mon Oct 30 1989 |
| Last Modified: | Mon Dec 31 1990 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 3726 |
| Total number of notes: | 19516 |
I've been using CHILD on VT terminals for some time now and I love it. Now I'm running it on a VS2000 with DECwindows and I still love it but I'm running into two problems. The first is that I want to suppress the FileView - Task Output window that tells me the identification of my process. Can this be done? The second is that I can't issue VUE$ commands in a command file that is run in a window created by CHILD. For example; ------------------------------------------------------------------------------ (from a FileView - Task Output DCL Command Window) $ CHILD/DECWINDOWS/TITL="VUE$ Test Window" (from the VUE$ Test Window) $ VUE$GET_SELECTION_COUNT %DCL-W-UNDFIL, file has not been opened by DCL - check logical name ------------------------------------------------------------------------------- The logicals VUE$OUTPUT and VUE$INPUT are not defined in the CHILD process. I think that this is causing the problem but I'm not sure how to fix it. Henry
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1139.1 | STAR::MFOLEY | Rebel without a Clue | Wed Jul 19 1989 16:21 | 8 | |
Try BULOVA::FILEVIEW mike Press kp7 or SELECT | |||||
| 1139.2 | AWOL | SK8R::CRITZ | Richard -- KB4N/1 | Wed Jul 19 1989 16:59 | 5 |
RE: .1 Might be a bit hard to do since BULOVA::FILEVIEW has been reported as AWOL by Notes all day today. | |||||
| 1139.3 | Okay, but how 'bout the Process Creation Notification? | SOJU::POZZETTA | Henry Pozzetta - SWSE/ACES Commercial CASE Technology | Fri Jul 21 1989 14:56 | 5 |
Can the process creation notification be suppressed? Is there a CHILD/NOLOG equivalent? HP | |||||
| 1139.4 | STAR::BENSON | Mon Jul 24 1989 11:03 | 12 | ||
For your first question, I assume you mean that you have a verb
defined which either invokes a command file to run CHILD, or runs CHILD
directly. You can suppress the task output box by including the task
message VUE$SUPPRESS_OUTPUT_POPUP at the start of your command file.
As for your second question, if CHILD is creating a new subprocess for
you, there's no way it will be able to communicate with the main
FileView process. FileView only wants to talk to subprocesses it
manages.
Tom
| |||||
| 1139.5 | CHILD is fully customizable | PRNSYS::LOMICKAJ | Jeff Lomicka | Mon Jul 24 1989 11:50 | 9 |
If you want a /NOLOG version, just locate the offending printf() in NEWPROC.C, and re-compile the sources. The sources and DESCRIP.MMS are all there in the release area. Note that it requires two .H files from the V2.4 or earlier release of C - I haven't yet updated it to work with the totally incompatible .H files that shipped with V3. | |||||
| 1139.6 | Compiling Child with VAXC V3 | IOSG::MARCHANT | Flaked out in the heat | Mon Jul 24 1989 21:14 | 26 |
I had the problem compiling child with VAXC V3, but the following
workarounds fixed it for me.
In NEWPROC.C add the following line *after* the #includes:
#define acc$record accdef
and in SETMODE.C comment out the the 'perform1' of HOLDSCREEN.
Differences follows (note I used #if 0 ...#endif instead of comment
delimeters /*...*/)
************
File USER2:[MARCHANT.CHILDSRC]SETMODE.C;2
218 #if 0
219 perform1( &tc, channel, device, "HOLDSCREEN", TT$M_HOLDSCREEN);
220 #endif
221 perform1( &tc, channel, device, "HOSTSYNC", TT$M_HOSTSYNC);
******
File USER2:[MARCHANT.CHILDSRC]SETMODE.C;1
218 perform1( &tc, channel, device, "HOLDSCREEN", TT$M_HOLDSCREEN);
219 perform1( &tc, channel, device, "HOSTSYNC", TT$M_HOSTSYNC);
************
Paul.
| |||||
| 1139.7 | SOJU::POZZETTA | Henry Pozzetta - SWSE/ACES Commercial CASE Technology | Tue Jul 25 1989 11:44 | 7 | |
RE .4 Thanks Tom. If I find anything about VUE$ commands in a CHILD subprocess, I'll post it here. HP | |||||