RE: DDS Window keywords

[KASHYAP VASWANI <kashyapv@xxxxxxxxxxxxx>]

Hi Chris,
        I think you can circumvent this problem by giving ASSUME keyword if you 
are trying to display some other screen from some other program that you are 
calling  from the parent program. This keyword cannot be  given on window 
record format so you make a dummy record format with a dummy field and give 
ASSUME keyword it will be applicable to all the record formats within that 
display file.  If this is not clear to you I will be glad to explain it you 
with example in the next mail.                            kashyapv@wipsys.ge.com

----------
From:   Chris.Chambers@v2music.com[SMTP:Chris.Chambers@v2music.com]
Sent:   Monday, February 15, 1999 5:52 PM
To:     midrange-l@midrange.com
Subject:        DDS Window keywords



I am using the WINDOW keyword to display pop up boxes over screens.

If I define the window as a format of the screen file being processed with
the keywords

WINDOW
OVERLAY

The window is displayed on top of the existing screen with the details
still visible behind it . . . . .GREAT.

BUT

When I define the window screen as a seperate file with the same keywords
it clears down the first screen and only shows the window screen in
isolation. I can get round this by specyfing USRDSPMGT on the window screen
file - but this is a dirty fix harking back to S/36 days and I'd like to
code it natively.

Answers please . . . . .


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

application/ms-tnef