Re: 4GL form won't fit on a screen

Path: emory!ogicse!sequent!muncher.sequent.com!lugnut From: lugnut@sequent.com Newsgroups: comp.databases.informix Message-ID: <1991Oct7.183403.25588@sequent.com> Date: 7 Oct 91 18:34:03 GMT References: <1991Oct2.233348.27406@vexcel.com> <1991Oct5.171602.13440@StarConn.com> <187026@unix.cis.pitt.edu> Sender: news@sequent.com (News on Muncher) Organization: Sequent Computer Systems, Inc. Posted: Mon Oct 7 11:34:03 1991 In article <187026@unix.cis.pitt.edu> smfst2@unix.cis.pitt.edu (Seth M Fuller) writes: >In article <1991Oct5.171602.13440@StarConn.com> pmahler@StarConn.com (Paul Mahler) writes: >>alanb@vexcel.com (Alan Baxter) writes: >> >> >>I want to use a screen form in 4GL for manipulating reseau calibration >>reports in a photogrammetric database. The problem is that a reasonably >>formatted form won't fit on one screen. >> >>What's a good way to handle this? It doesn't look like the screen array >>was designed for the case where one row won't fit on a screen. Should I >>distribute the calibration values over multiple screens and have the >>user use a menu to move between screens? Is there a better or more >>standard way to handle this? >> >>Alan Baxter (303)444-0094 alanb@vexcel.com > >One thing that you could do is have a pop-up window with the rest of the >screen in it. You could access the window with a function key in your first >screen. In this way you would get as close as possible to have everything >on one screen. When the user wanted to edit/view the stuff that wouldn't >fit on the first screen it is only a function key away. When the user exits >the window his other screen is right there underneath (if you close the >window of course). > The "window" works.. Depending on what you want the mechanisim to "look" like, a function key may be un-needed, eflastkey testing after field can be used for opening a window. By nesting inputs (and screen calls) in an input function using a while loop with a case to control which segment goes where. (I have a single screen for example that uses 5 different input statements that are completely transparent to the user with a mechanisim that allows the user to move forward or backwards thru them without using a control key to do so. 4gl's array handeling could be better but, with a little diligence and some creative thinking *anything* is possible. (it may take 2500 lines of code though) :-) Don "what structure?" Bolton