× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Good Catch.

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Wintermute, Sharon
Sent: Tuesday, October 05, 2010 9:29 AM
To: RPG programming on the IBM i / System i
Subject: RE: Popup windows in subfiles

What is happening is that when you use LR on exit from the second
routine, the first routine (if RSTDSP = *YES) knows it needs to
redisplay the subfile. But, since you are calling the second routine
again before any read on the subfile control, it blanks the screen
before it displays the popup.

IIRC, An easy way to not get the blank screen is to use RT on the pop-up
window. Since it will "remember" that the last screen displayed was the
popup. Use RSTDSP(*YES) on both display files.



Sharon Wintermute

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of
joepluta@xxxxxxxxxxxxxxxxx
Sent: Tuesday, October 05, 2010 12:26 PM
To: RPG programming on the IBM i / System i
Subject: Re: Popup windows in subfiles

Anybody run into this? I've got KEEP and ASSUME on a DUMMY record
format
in screen 2. I've changed the RSTDSP parameters to all four
combinations
of *YES and *NO on the two programs. The programs themselves are RPG
programs compiled with DFTACTGRP(*YES). Both set on *INLR when they
exit.

Forgot the salient release info: V5R4 with cume from 2009.

Joe

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.