PxPlus User Forum

Main Board => Discussions => Thin Client/WindX => Topic started by: Floris Netten on July 04, 2018, 04:33:25 AM

Title: When starting a program the panel is not visible on screen
Post by: Floris Netten on July 04, 2018, 04:33:25 AM
Hi all,

when users start a program with a panel, sometimes the panel is not visible on screen. Mostly it is "below"  the screen, the only way to get it shown is to move the panel into the screen.
Unfortunately the programs it happens to differ from user.

We mostly use multiple monitor setups and windows 7 as os, we use the windx client

Anybody has experience with these hidden panels?
Title: Re: When starting a program the panel is not visible on screen
Post by: Tino on July 04, 2018, 08:06:35 AM
Floris,

What version of pxplus ?
Do you use  *winpnl?    if yes, locate the record in *win/panel.inf that corresponds to that user/panel/library  and remove that record.

Regards,
Tino


Title: Re: When starting a program the panel is not visible on screen
Post by: Mike King on July 04, 2018, 05:44:07 PM
Generally when a panel is started by Nomads, the position is determined either by its last panel position (assuming you have persistence enabled -- see below) or the settings on the panel header.

On the panel header you can specify the location of the panel and a line/column specification.  There are three options:


Panel Persistence
Nomads provides the ability for the system to remember where you last placed a panel and will attempt to restore it to the same position.  This is done generally by setting %Nomads'Panel_Info_Prog$ (%Nomad_Panel_Info_Prog$) to the name of program which will save and recall the panel position. 

We supply a program "*winpnl" that does this for you.  It preserves the last location a panel was placed by user id in the file called "panel.inf".  Simply call *winpnl prior running any Nomads based application and the system will enable persistence.

You can write your own program to do the same if desired, but generally *winpnl provides the necessary functionality.

Your Problem
You indicated that the position is wrong.  Is it possible that you have multiple workstations using the same user id?  This could cause confusion if you are using the standard *winpnl program.