Either way, a good start will pay dividends for years as some of the most powerful features of the language are not easily spotted reading the web documentation and was not covered in basic training.

I've been looking for some of this kind of "hidden in plain sight" stuff. Osmosis doesn't always work too efficiently.

When processing some panels from our menu program, the font sizes in (typically) Multi_Lines and List_Boxes are inconsistent -- even on the same machine. I just saw one that had everything fitting properly, then cycled through the menu, and it became a larger size, perhaps 1 or 2 points, but enough to overflow the field sizes.

Does anyone have any idea what might cause this? It's been plaguing us for months. This is the first time I've been able to see this dynamic a change, and there's nothing I've been able to find that might be the culprit.

PxPlus 13.10, RHE Linux 5, *nthost/*ntslave WindX

Mike:
Does this mean the limit on recursive calls has been eliminated? Or changed?
According to the documentation, one of the reasons for throwing Error #25:

Cannot exceed limit on number of recursive calls to a user defined function. (Maximum of 10 recursive calls, ten levels deep.)

Or does defining the function with Local variables override the limit?

Thanks in advance for the clarification.

You could look into XEQ as a possibility:
https://manual.pvxplus.com/PXPLUS/functions/xeq.htm

We've got a printer selection panel that we can flag to run in "Silent Mode" - a default selection is made, the open processing is executed, and returns to the calling program without displaying the actual panel.

Some of our calling programs will call this routine multiple times to create disk files instead of using an actual printer. While debugging some program mods, we noticed that one of our system files that gets opened for this panel doesn't seem to always be closed on exit, and sometimes dozens of channels are in opened for this single file.

The Pre-Display is to Perform ";Init_Prog"
The Post-Display (which in this case should not be used) is to Perform ";Start_Up"
The On Exit is to Perform ";Wrap_Up"

There are 2 system files opened in Init_Prog. If running in Silent Mode, the end of the Init_Prog routine GOSUBs to the open-printer routine, sets Cmd_Str$="END", then RETURNs.
The Wrap_Up simple closes the 2 system files, resets a global variable, and RETURNs.

The curious part of it all is that the 2 system are both opened and closed in adjacent lines, but only 1 seems to get closed -- most of the time. The channel variable names are PRT_FILE and FORM_FILE, with the latter being the one that seems to remain open.

For the debugging today, it seems to have been called about 1300 times, and left behind about 100-125 open files that should have been closed. Most of them were the FORM_FILE, with a handful of the PRT_FILE.

Has anyone run into anything like this before? Is there something that's not getting set correctly when bypassing the Display Panel process?

Thanks in advance for (1) reading through this, and (2) any suggestions you may have.

While the forum seems to have made it to 2019, the main PxPlus.com website doesn't respond as being alive. This includes the online manual.

Mike:
I've tried importing this into our v13.10 PxPlus Nomads, but all I get is "No panels available"
Anything I should tweak to get it in?