Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!hao!gatech!purdue!i.cc.purdue.edu!j.cc.purdue.edu!pur-ee!iuvax!bsu-cs!cfchiesa
From: cfchiesa@bsu-cs.UUCP (Sir Xetwnk)
Newsgroups: comp.os.vms
Subject: Re: FMS
Message-ID: <2207@bsu-cs.UUCP>
Date: 25 Feb 88 19:12:03 GMT
References: <5050@ames.arpa>
Organization: CS Dept, Ball St U, Muncie, Indiana
Lines: 25
Keywords: FMS, SMG
Summary: FMS again

In article <5050@ames.arpa>, pstevens@pioneer.arpa (Paul Stevens RCE Sterling) writes:
>    [his two cents on FMS vs SMG]
 
> For fancier applications (like the drop down menu's mentioned earlier)
> I think SMG may be the only choice.  I'm not sure but I also think that
> SMG may be better at handling different types of terminals.

I think you can do the equivalent of "pull down menus" by overlaying one
form on another in FMS; you have to define separate workspaces for them, if
I've understood the (somewhat vague) documentation properly...  I haven't
messed with this very much, and what I HAVE done is kind of a 'kludge', in that
I get one form displayed over the bottom half of another, but if you REFRESH
the screen you only get the CURRENT one, not BOTH with the second occluding
the first.  I don't know if this would happen if I were doing the double-
workspace bit...  I suspect it would refresh to the actual intended "overlaid"
appearance of the screen.  Anybody mess with this and know for sure?

Chris Chiesa, Senior, Ball State University, Muncie, IN  


>  
-- 
<><><><><><><><><><><><><><><><><><><><><><><><><><><><> Chris Chiesa <><><><><>
<> {ihpn4|seismo}!{iuvax|pur-ee}!bsu-cs!cfchiesa                              <>
<> cfchiesa@bsu-cs.UUCP                                                       <>
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>