|
Well, QCMD is a *DS3 (24*80) screen.
And tour window is also *DS3?
If not, the background turns black and does not show the first screen the window was displayed on, as a background.
Kind regards,
Carel Teijgeler
Op 19-7-2018 om 21:28 schreef Paul Therrien: I am currently in development mode so I am calling the test program
directly from a command line.
In one instance I am calling the window program directly from the
command line.
in the other instance I am calling an rpg program from the command line
that executes a procedure in a service program that invokes the window
program.
So in both cases the underlying screen is QCMD.
Paul
On 2018-07-19 15:18, Carel wrote:
Does the previous screen has a different format then the new screen? *DS3 v. *DS4.
Kind regards,
Carel Teijgeler
Op 19-7-2018 om 15:33 schreef Paul Therrien:
I have a window display program that, when called directly, the window
pops and the screen behind remains on the display. - All good.
When I call this same program from within a service program the window
pops, but the screen behind is erased; so all i see is the window, with
a blank screen behind.
The window operates fine in both circumstances, it is the erasing of the
screen behind the window that is an issue.
Is there a way to retain the screen data behind from within a service
program?
Am I, again, misunderstanding something?
Thanks for any help.
Paul
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.