Re: putting up a screen over another one

boothm@earth.goddard.edu wrote:
> 
> I just came across another thing I would like to do, seems like it could
> be done, but I can not figure out how.
<snip>
> 
> So, what I was thinking is this:  Can a screen be delayed before being put
> up?  Could I in fact invoke the next program, put up the correct screen,
> and then have a window pop up with the five lines of prose from the
> original program?  

Without giving it a try myself, I would start with one display file for
all of the concerned programs compiled with DFRWRT(*YES) and SHARE(*YES)
therefore each record would not be actually displayed until a record
with either a FRCDTA(Force data) or  INVITE keyword was active.

Program 'A' would write out the 5 line prose you described without
either a FRCDTA or INVITE, program 'B'  (sharing the file ODP) would
perform a write with INVITE might, and I do think might,  force the
program 'A' panel and the program 'B' panels to appear at the same
time.  You may need a record never used, but defined, in the DDS which
contains the ASSUME keyword to prevent screen blink.

Just a thought.....
-- 
===================================================
James W. Kilgore   | Progressive Data Systems, Inc.
President          | 311 31st Ave SE
(206) 848-2567     | Puyallup, Washington 98374 USA
qappdsn@ibm.net    | http://www.ultimate.org/PDS
===================================================
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *