Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!bbn!oberon!cit-vax!ucla-cs!zen!ucbvax!LBL.ARPA!nagy%warner.hepnet
From: nagy%warner.hepnet@LBL.ARPA (Frank J. Nagy/VAX Guru)
Newsgroups: comp.os.vms
Subject: Questions on VMS Workstation Software: In UIS, how do you...?
Message-ID: <870928060020.040@Lbl.Arpa>
Date: Mon, 28-Sep-87 09:00:20 EDT
Article-I.D.: Lbl.870928060020.040
Posted: Mon Sep 28 09:00:20 1987
Date-Received: Tue, 29-Sep-87 05:43:33 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 38


    What we want to do is to be able to use the mouse in the VT220
    window.  We want to write applications to use (primarily) SMG
    and run on both real VTxxx terminals and VT220-emulator windows
    on the VAXStation - we know that works.  What we want is to be
    able to use the mouse with the VT220 window on the VAXStation to
    control the text cursor.  On a real VTxxx terminal, the user will
    move the text cursor to a field with the arrow keys and then hit
    the carriage return or some other key (application-specific probably)
    to select that field and cause some action which is dependent upon
    the field selected.
 
    On the VAXStation, we want to allow the user to use the mouse to
    do the field selection, but we would rather NOT have to provide
    a complete UIS implementation of the application in parallel with
    the SMG implementation.  We would be willing to supply some UIS
    code in parallel to the SMG code; this UIS code would accept mouse
    events and report them to the application to simulate the actions
    normally taken via SMG and the keyboard.
 
    Any ideas, suggestions, helpful hints?  Any DEC developers listening
    out there?
 
    We believe one way to do this with our extra UIS code could be done
    if we had the window id of the VT220 emulator window.  Can UIS window
    ids be passed between processes (i.e., process #1 create a window
    and pass its id to process #2 in some manner and have process #2
    call UIS routines with that window id)?  This question arises from
    observing the existance of a UIS$EMULATOR process from SHOW SYSTEM
    on our VAXStations.  We believe this process creates and manages
    the VT emulator windows and so has the necessary window ids.
 

= Frank J. Nagy   "VAX Guru"
= Fermilab Research Division EED/Controls
= HEPNET: WARNER::NAGY (43198::NAGY) or FNAL::NAGY (43009::NAGY)
= BitNet: NAGY@FNAL
= USnail: Fermilab POB 500 MS/220 Batavia, IL 60510