[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

1055.0. "input = DECwindows, output = terminal ??" by KETJE::PUTMANS (Close that Window, please) Tue Jul 04 1989 09:32

Hi,

we want to convert a terminal-i/o application to DECwindows.
we want to do the INPUT with DEC-toolkit (UIL)
and the OUTPUT with terminal-QIO

can someone point me or give me some hints how to start, and where to look...

for input ---> UIL (i think i can manage that)
for output --> DECterm widget ?

Eric.

T.RTitleUserPersonal
Name
DateLines
1055.1Yep5319::LOMICKAJJeff LomickaWed Jul 05 1989 11:204
It might be slightly easier to start with DecwTermPort, but what you
have said is the correct approach.


1055.2Play with DECwindows EVEEVETPU::REINIGThis too shall changeWed Jul 05 1989 13:0812
    Not that it is of much use, but if you go into DECwindows EVE and
    delete the message buffer:
    
            DO buf messages
            DO tpu delete (current_buffer)
    
    Then all of EVE's input comes from the toolkit.  Most of its output
    goes to the toolkit.  That output destined for the now non-existent
    message buffer goes to sys$output.  Rather an odd state of affairs.
    
                                    August G. Reinig