RE: RSTDSP NOT WORKING

Neil,

    <<<<and when you call
    <<<<program C the RSTDSP keyword now saves a blank buffer to restore
    <<<<when you return from program C.

Returning from program C doesn't cause the problem. Program C pops up a
window over a blank screen. The problem is the screen was not restored when
returning to Program A from Program B. I wrote a quick test program to test
this. Program A presents a screen and calls Program B which pops up a
window over it. Press enter and it returns to Program A which then goes
into a loop. After pressing enter in Program B you see a blank screen. It
wasn't restored.

    <<<<If you wrote a display for program A before the call to program C
(maybe
    <<<<some dummy display format that writes a line at the bottom of the
screen
    <<<<or something) it probably works fine (maybe this is the workaround
you
    <<<<used ?).

I hadn't thought of writing a dummy format. We just write one of the
formats that was on the screen before we left the program. This works, but
causes headaches because the screen has to be compiled with DFRWRT(*NO) in
order to work. Also, you have to be sure that you're not losing data in any
of the fields by re-writing it. But  like the dummy format idea better.
I'll give that a try.

    <<<<I assume you've tried RSTDSP on all screens for programs A, B & C
and it
    <<<<made no difference ?

Yep

    <<<<Have you tried putting all display formats for programs A, B & C
into one
    <<<<display file, and using the same display file for all 3 programs ?

This would work of course, but runs contrary to modular programming
techniques. What if Program C is also called from Program D?
Ron Hawkins

+---
| 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
+---