|
midrange.com
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--
[ Picked text/plain from multipart/alternative ]
Hello,
I ask the Keep and USRRSTDSP question in another post to learn if maybe it
would help with my post on Mouse Buttons
When returning from window pgmb(restore display *yes, mouse button
rec selection, scroll,push buttons) to screen pgma(restore display *yes)
with a selected value for a specific subfile record and the user clicks
mutiple times, with left(enter) mouse (through client access) in non input
area of screen, they get permanant I/O error(CPF5192) on exfmt of screen.
Normal keying and mouse usage seems OK. Any ideas will be greatly welcome.
I have a write of a shared header screen record(used as top to numerous
screens just output) before exfmt(input/output), both have OVERLAY.
example
pgma
write scrnhdr rec- with overlay -used as header to other screens in program
exfmt scnrbot rec- with overlay -this screen has f4-prompt field
f4- prompt calls pgmb window subfile
A DSPSIZ(24 80 *DS3)
A REF(*LIBL/DDSFLDS)
A PRINT
A PAGEDOWN
A PAGEUP
A R DUMMY
A*%%TS SD 20020319 161255 BHOPKINS REL-V5R1M0 5722-WDS
A ASSUME
A 1 3' '
A*
A R DFTSFL SFL
A*%%TS SD 20020821 074154 BHOPKINS REL-V5R1M0 5722-WDS
A CHGINPDFT
A SSEL 1A I 6 2DSPATR(UL)
A DSPATR(HI)
A SSWO# R O 6 5REFFLD(ONUM)
A SSDTIN R O 6 12REFFLD(DATM)
A EDTCDE(Y)
A SSCUST R O 6 21REFFLD(CST#)
A EDTCDE(4)
A SSSPTO R O 6 28REFFLD(DST#)
A EDTCDE(4)
A SSPART R O 6 32REFFLD(PART)
A SSQTY R O 6 48REFFLD(QTY)
A EDTCDE(4)
A SSLOC R O 6 54REFFLD(BIN)
A SSSDAT R O 6 61REFFLD(DATM)
A EDTCDE(Y)
A SSSTS 2A O 6 70
A SSAREA R O 7 18REFFLD(AREA)
A DSPATR(UL)
A SSCTGM R O 7 27REFFLD(CTGM)
A DSPATR(UL)
A SSCTGY R O 7 36REFFLD(CTGY)
A DSPATR(UL)
A SSPO# R O 7 49REFFLD(PO#)
A DSPATR(UL)
A 7 12'Area:'
A DSPATR(HI)
A DSPATR(UL)
A 7 21'MCat:'
A DSPATR(HI)
A DSPATR(UL)
A 7 31'Cat:'
A DSPATR(HI)
A DSPATR(UL)
A 7 44'PO#:'
A DSPATR(HI)
A DSPATR(UL)
A R DFTCTL SFLCTL(DFTSFL)
A SFLSIZ(0007)
A SFLPAG(0006)
A WINDOW(DFTCMD)
A CF11
A CF06
A CF12
A KEEP
A BLINK
A OVERLAY
A PUTOVR
A SFLCSRRRN(&RRNA)
A SFLMODE(&FOLD)
A 32 SFLDSP
A SFLDSPCTL
A 30 SFLCLR
A 99 SFLEND(*SCRBAR *MORE)
A 36 SFLDROP(CF11)
A N36 SFLFOLD(CF11)
A 60 SFLMSG('ROLL UP OR DOWN BEY
A T OR LAST RECORD IN SUBFILE
A MOUBTN(*ULP *ULD ENTER)
A SFLPSD 4S 0H SFLRCDNBR(CURSOR)
A FOLD 1A H
A RRNA 5S 0H
A 2 3'Type a (1), then press ENT
A 4 5'Position to..'
A SPOS R I 4 19REFFLD(ONUM)
A COLOR(TRQ)
A 4 28'(W.O.#)'
A 5 1'Act'
A DSPATR(HI)
A DSPATR(UL)
A 5 5'WO# '
A DSPATR(HI)
A DSPATR(UL)
A 5 12'WO Dat '
A DSPATR(HI)
A DSPATR(UL)
A 5 21'Cust# '
A DSPATR(HI)
A COLOR(WHT)
A DSPATR(UL)
A 5 28'Shp'
A DSPATR(HI)
A DSPATR(UL)
A 5 32'Item# '
A DSPATR(HI)
A DSPATR(UL)
A 5 48' Qty'
A DSPATR(HI)
A DSPATR(UL)
A 5 54'Loc '
A DSPATR(HI)
A DSPATR(UL)
A 5 61'Shp Dat '
A DSPATR(HI)
A DSPATR(UL)
A 5 70'St'
A DSPATR(HI)
A DSPATR(UL)
A R DFTCMD
A WINDOW(2 1 20 75)
A WDWBORDER((*COLOR TRQ) (*DS
A (*CHAR '********'))
A F2 2Y 0B 19 2PSHBTNFLD
A CHCAVAIL((*COLOR PNK))
A PSHBTNCHC(1 'F>12-Cancel ' CF12)
A PSHBTNCHC(2 'F>11-Fld/Unfld CF11)
A PSHBTNCHC(3 'F>6-Show' CF06)
Sorry so much.
Could there be a translation delay between to the write and exfmt with the
Mouse Click????
Was hoping KEEP and USRRSTDSP might be answer.
All replys welcome.
Thanks Bill Hopkins
Bhopkins@saurerinc.com <mailto:Bhopkins@saurerinc.com>
-----Original Message-----
From: qappdsn@attglobal.net [ mailto:qappdsn@attglobal.net
<mailto:qappdsn@attglobal.net> ]
Sent: Thursday, August 22, 2002 12:36 PM
To: rpg400-l@midrange.com
Subject: Re: Keep background screen on display when using window keyword
Bill,
I'm not sure if this answers your questions or not, but we use the KEEP
keyword to prevent the screen from 'blinking' when you exit programs.
For example, pgmA puts up a display then calls pgmB which puts up a display.
We have found that without the KEEP keyword, as the user exits pgmB the
screen will go blank for just a split second before the display from pgmA is
restored.
It doesn't seem to matter if you have RSTDSP(*YES) or USRRSTDSP, without the
KEEP, it blinks.
IBM's example shows a single display file. This brings up a different set
of issues than if you have a separate display file for each program.
I've lost the original post, but are you using a single or multiple display
files? If it is a single display file are you using a shared ODP?
The reason I ask is that we use a single display file for all related
programs (ie: xxxxWRK, xxxxEDT, xxxxADD, etc.) and have a shared ODP and do
not experience background screen loss.
J. KIlgore
_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
<http://lists.midrange.com/cgi-bin/listinfo/rpg400-l>
or email: RPG400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l
<http://archive.midrange.com/rpg400-l> .
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.
