home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cs.utexas.edu!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!emory!emory!not-for-mail
- From: inf_bb@hermes1.sps.mot.com (informix users bb)
- Newsgroups: comp.databases.informix
- Subject: Re: 2 questions: 4GL source length limit & screen redraw question
- Date: 12 Jan 1993 16:38:06 -0500
- Organization: Mailing List Gateway
- Lines: 29
- Sender: walt@mathcs.emory.edu
- Distribution: world
- Message-ID: <1ivdnuINN5vh@emory.mathcs.emory.edu>
- Reply-To: inf_bb@hermes1.sps.mot.com (informix users bb)
- NNTP-Posting-Host: emory.mathcs.emory.edu
- X-Informix-List-ID: <list.1775>
-
- paul,
-
- im not sure about your first question on size of program modules,
- but the second one:
-
- 2) With ^R to redraw the screen and Informix refreshing underlying windows
- when one is closed it makes sense to think there is some sort of
- data structure keeping track of what the screen should look like. I
- would appreciate any information to access that structure. In this case
- I would like to dump the current screen to a file/printer from an
- ON KEY(whatever) CALL dumpScreen() type senario.
-
- yes, there is a way to print the current screen. you must first set the
- DBSCREENOUT environment variable to the name of the file you want to
- save the screen to. then just run the program and hit CONTROL-P as many
- times as you like. the screen images will be appended to the file named
- by DBSCREENOUT.
-
- regards,
-
- ------------------------------------------------------------------------------
- | . .
- Bob Baskett | ... ...
- Software Engineer, DBA | ..... .....
- Business Systems Integration Group | .. ... ..
- Semiconductor Products Sector | . . .
- Mesa, AZ |
- | Motorola, Inc
- ------------------------------------------------------------------------------
-