[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference bulova::decw_jan-89_to_nov-90

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

3622.0. "Window passthrough?" by NITMOI::ARSENAULT () Fri Nov 09 1990 11:23


I'm new to the DECwindows programming environment and as such, I'm kind of
stuck, looking for some suggestions/answers.

Bascially, I've got (in theory) a modularized program capable of executing
in different environments, automatic and interactive.  While in automatic
mode, no user interaction is necessary, therefore, the DECwindow/UI routines
will not be activated.  However, while in interactive mode, the program will
execute the associated function in such a way to activate its language
interpreter.  Before the main program calls the function (with the interpreter
activated), is there a way to redirect this I/O to a window?

I've played around a little bit with a DECterm, but I don't want to create a
process for that DECterm because the program is already activated and can
dynamically activate or deactivate its interpreter.  A command window appears
to be a consideration, but I don't really want to 'know' about the details of
what is going on within the interactive (interpeter) session.

Is there a way to redirect sys$input, sys$output to a window on an active
process dynamically?

-(dan)

T.R Title User Personal
Name Date Lines

3622.1 use a pseudo device? VINO::MCARLETON Reality; what a concept! Fri Nov 09 1990 14:29 29

T.R	Title	User	Personal Name	Date	Lines
3622.1	use a pseudo device?	VINO::MCARLETON	Reality; what a concept!	`Fri Nov 09 1990 14:29`	29
	I wrote an application that uses the DecwTermPort routine to create DECterm window for a running program. I have the advantage that I can assign the logicals sys$input and sys$output to point to the DECterm before the image opens it's I/O channels. If your image has already opened sys$input and sys$output you would have to implement some kind of pseudo device so that you could redirect the output. In VMS 5.3 you would use the PY/TW driver. In 5.4 you would use the FT driver. It would look like this: Automatic: ----- ------------- \|app\| \| \| QIO \| \| --->\|TWAn: PYAn:\|---->output file \| \| \| \| ----- ------------- Interactive: ----- -------------- ----------- \|app\| \| \| QIO \| DECterm \| \| \| --->\|TWAn:..PYAn:\|---->TWAy:--->\| window \| \| \| \| \| \| \| ----- -------------- ----------- The program would always be talking to TWAn: but the output of PYAn: would be redirected to a log file or the DECterm as needed. MJC

    I wrote an application that uses the DecwTermPort routine to create
    DECterm window for a running program.  I have the advantage that I
    can assign the logicals sys$input and sys$output to point to the
    DECterm before the image opens it's I/O channels.

    If your image has already opened sys$input and sys$output you would
    have to implement some kind of pseudo device so that you could redirect
    the output.  In VMS 5.3 you would use the PY/TW driver.  In 5.4 you
    would use the FT driver.  It would look like this:

    Automatic:
    -----     -------------                             
    |app|     |           | QIO
    |   | --->|TWAn: PYAn:|---->output file
    |   |     |           |
    -----     -------------

    Interactive:
    -----     --------------              -----------  
    |app|     |            | QIO          | DECterm |
    |   | --->|TWAn:..PYAn:|---->TWAy:--->| window  |
    |   |     |            |              |         |
    -----     --------------              -----------

    The program would always be talking to TWAn: but the output of PYAn:
    would be redirected to a log file or the DECterm as needed.

    						MJC