PxPlus User Forum

Main Board => Discussions => Thin Client/WindX => Topic started by: Patrick Denny on October 06, 2025, 03:35:20 PM

Title: VIEWER print preview - set system parameter for keep alives
Post by: Patrick Denny on October 06, 2025, 03:35:20 PM
Re: Sending printer output to *VIEWER* / VIEWER

How can I set a system parameter, specifically '+A'=1, for "Keep Alives" when using the *VIEWER*?

I am able to keep my running programs alive using:
    SET_PARAM '+A'=1
in my START_UP program when launching Windx (appserver).

But the *VIEWER* always times out after X amount of time.

I would appreciate if you can include an example rather then just making a statement like "include it on the OPEN command".

I have tried including: -+A=1  (and various iterations and positions in the target line)
on the "target line" on the windows shortcut, but this parameter must be one of the parameters that pxplus doesn't recognize when passed on the target line.
Title: Re: VIEWER print preview - set system parameter for keep alives
Post by: EVa on October 07, 2025, 10:32:37 AM
When using WindX with the application server, opening the viewer causes a new WindX session to be started (through the *server/*client programs).  This means that PxPlus will execute the START_UP program (on the WindX side of the connection).  Just create a START_UP program with these contents (on the WindX PC - or create it on the server and move it to the WindX PC as you can't create programs {easily} on the WindX side of the connection):

0010 ! START_UP
0020 MSGBOX "You're in "+PGN,"Info"
0030 SET_PARAM '+A'=1
0040 STOP

When you open a viewer, you should see the msgbox appear.
Title: Re: VIEWER print preview - set system parameter for keep alives
Post by: Patrick Denny on October 13, 2025, 08:08:04 PM
Thanks for the reply, but...

I setup the START_UP program, and it is being executed, but the VIEWER window still suffers from "connection dropped" issues after so long. I had another window open for editing code which was left unattended for about 1.5 hours and that window remained "alive" while 2 other VIEWER windows "crashed" when I switched back to them.

Is there something else or more I could do to prevent the VIEWER sessions from crashing?
Is a setting of '1' the appropriate value to be using?

Obviously there is "inactivity" on the VIEWER connection.  Is there something more that could be done to "create activity", if that makes sense or is possible?