Re: Refreshing a kiosk screen

[Luke Gerhardt <lgerhardt@xxxxxxxxx>]

 You have to use the INVITE keyword, true.  You also must change your 
EXFMT to a write/read combination.  If you have subfiles there is a bit 
of a hurdle with INVITE, so you have to condition it to turn it off when 
you want to read a subfile...confusing, I know.  :)

Oh, and you must specify WAITRCD on the display file.  It's how many 
seconds you want your WRITE to wait before automatically proceeding.  
Here's an example (yes, those are really the source comments):

// turn on dds invite keyword and write the control record
*in81 = *on;
write FTR;
write CTL;
// because we are using the dds invite keyword, we must use read with 
the format
// name of the display file, instead of using exfmt with the record name
read(e) V000X;
...
// The dds invite keyword is cool, and lets us create a screen that 
refreshes itself...
// but, it is mutually exclusive to subfile manipulations such as 
reading and clearing.
// So we have to condition the invite keyword so that we are not 
inviting when we try
// to do subfile work...  Turn the indicator off and write the control 
record again in
// order to cancel the invite.
*in81 = *off;
write CTL;
readc SFL;


On 8/5/2010 1:00 PM, rpg400-l-request@xxxxxxxxxxxx wrote:
> date: Thu, 5 Aug 2010 11:49:20 -0500
> from: "Bob P. Roche"<BRoche@xxxxxxxxxxxxxxxxx>
> subject: Re: Refreshing a kiosk screen
>
> It's been a  few years since I've done this, but there is a way in a green
> screen application to refresh the screen. It's perfect for Kiosk usage. I
> had to abandon it because it removed the keyboard buffer and stray enter
> key presses would get inserted in to my code by an impatient user who
> presses the key several time "just to be sure" whenever they would process
> a certain screen. I remember the INVITE keyword being used, I can look it
> up again if you are using a green screen.
>   If it's web based I'm sure someone more knowledgeable than me can answer
> it form that angle.