We're running a character-based menu system that will run an existing CUI program or PROCESS a NOMADS panel, based on file parameters. I've created a new NOMADS F/M and when I exit by clicking the appropriate button, all is well. However, when I use the Alt-X hotkey I have set up for the Exit button, I get unexpected characters in the menu program's typeahead buffer.

We have other panels that are PROCESSed off the menu without incident, but this one, for some reason, works differently. (We're not using the NOMADS Security processing.) It's a panel with a few controls, a TitleBar, an embedded panel, and a folder on it. We have 2 options: Full Access and Inquiry Only, based on a file-based permissions list. The menu starts the Full Access version with 7 tabs on the folder, but if the user is identified as Inquiry Only, part of our Pre-Display routine PROCESSes a 3-tab version and exits with Cmd_Str$="END". While it doesn't seem to make any sense that there would be a difference, the 7-tab Full Access version drops "BN" into the input buffer, while the 3-tab version drops "BL" in. If I include a PRINT 'CI', in the Exit button's logic, the characters don't show up.

Any insights would be appreciated!

We're running PxPlus v15.10 on Linux RedHat with WindX on Windows 10 Pro workstations.

Is there a way to synchronize the horizontal scrolling of 2 list_boxes? The panel isn't wide enough to display the full width of the main list, which has the detail lines. We're setting up a second list of 1 line that has the totals for certain columns in the main list. By synchronizing them, the totals will always appear below the columns they refer to.

Similarly, if the user changes a column's width, is there are way to detect that and replicate it in the other list?

Thanks in advance, all!

While testing/preparing to use split files, I ran into a situation with an embedded io routine. In multifile.pvc, the Do_Pre_Write routine does its thing until it gets to:
if IoType=1 then write lock record (Chnl[_Found_chnl],key=_key$)_rec$ else write lock record (Chnl[_Found_chnl])_rec$
!
if and(_opt,64)=64 then gosub Extract_Update else extract release (lfa); gosub Extract_Free
Our embedded io routine does some post-write processing. This is called by the write lock record directive. It opens a reference file, reads it, then closes it. (There may also be some additional writing, based on results of this read.) Since _opt is 0, the next code line tries an extract release for lfa, but lfa was not the Chnl[_Found_chnl] in the write line. Changing lfa to Chnl[_Found_chnl] in the extract release line works fine in this situation.

However, there are other references to extracts and lfa elsewhere that I haven't gone through yet. These may be affected by post-read and post-write routines in embedded io routines.

Thought you'd like to know...

Could there be a link in the documentation from the OPEN directive to the File Handling -> Processing Data Files -> Accessing Directory Files page, perhaps even to the Special Directory Processing paragraph...?

I use it enough to know what's there, but not enough to know exactly what is where.

Thanks!

The current documentation lists the window size limits as 255 lines by 255 columns. The Release Notes for PxPlus 2021 (v18) state that (for NOMADS-oriented components) "Increased panel and control sizes to a width of 620 and height of 255 in all designers". We're currently on v15, and close to moving to v18. We just ran into a user with a monitor capable of 312 columns. The program has been patched to limit this to 255.

I presume the new window size limits are in effect for more than just NOMADS, and that we can address the larger monitors appropriately. However, I couldn't find any other documentation regarding those larger size limits. Could someone confirm that they are supported, or if this is a NOMADS-only implementation.

Thanks in advance!

I've got a panel with a couple of standard multi-lines, some buttons, a folder with 7 tabs, and 2 other multi-lines used as "traffic lights" to indicate whether the current record's process is Enabled or not. The status is controlled by a checkbox on the first tab. Both are locked and hidden/shown based on Dependencies.
The Enabled status is fine: Black text on Light Green background.
The Disabled status is strange: It's defined as White text on Light Red background. When first Shown, it comes up as Black on Light Red. It's only after a secondary panel is PROCESSed through a folder panel that it shows up as White on Light Red. If we return to the tab with the Enabled checkbox, it returns to Black on Light Red. (See attached.)
The library defaults have the colors set to Black on Light Gray.
Running PxPlus v15.1 with WindX on Linux.

Any ideas/suggestions?

I've got a multi-line field with both validation and formatting routines attached. If a value is entered into the field and the user mouse-clicks into a different field, it seems like the Validator is skipped, but the Formatter is not.
Is this correct behavior? I thought the Validator would check on any exit from the field.

Last weekend, I had some automatic updates done to my Windows 10 PC that caused some problems with the PxPlus Excel object. I'm not sure exactly what component changed, nor to what degree, and was wondering if anyone else had experienced this.

We've been able to create an Excel workbook from PxPlus with a null filename, and it would accept it, assuming something like "Book1.xlsx" in the "[My] Documents" folder as the default filename. After the update, this didn't work anymore. It took quite a while to narrow down, but I eventually discovered that a null filename could no longer be supplied to the CreateWorkbook method. Providing a name resolved the problem.

I know the PxPlus Excel object did not change. I'm not sure what else did. Others on our team have not yet been updated, so they're not experiencing this...yet.

Has anyone else run into this problem? Is this something that can be corrected, or do we just have to work around it like we have?

Thanks, all!