Hello all. Using PxP 2024. This concerns the element written using the variable name Obj_Orig$ under a panel header (0000) rec in the panel library file.

I've noticed that in Library Compares, the reports are now starting to show

Customization was "panelAname"
                          now "panelBname"       [or one of the entries could be ""]

I examined the panel compare pgm, and I see that this is not a new thing; i.e. that "Customization" line has been in there for at least a few versions before 2024. And that Customization corresponds to Obj_Orig$.

My hunch is that panels edited now get the name of the panel written to Obj_Orig$ in its 0000 rec when saved in PxP 2024. Because when I looked at existing older panels, they have null in Obj_Orig$, whereas the ones edited in 2024 have it populated.

What's happening now as a consequence of this is that compared panels that normally do not have any differences between them now produce a report with that Customization as the only reported difference in the panel header section. Can someone explain why this is, why it's necessary?

Thanks!

Paula McKeever
CAI Software LLC

Ah, so I take the "Search All" means all of the elements represented by the checkboxes and nothing further?

Many thanks, Susan! Any chance I could be in the loop to be notified when the fix is done?   

Greetings. Using PxP 2024. When I did a Search in Nomads for a routine in a Dependency Definition's logic, it did not get a hit when it turns out in fact it does exist.

E.g. the DD read Perform="SomePgmName;Some_routine"
I had it search for Some_routine.

I chose "Select All", and ensured that the search was case insensitive.

Does the search engine exclude DDs? If so, why?

Thanks in advance.

Paula McKeever
CAI Software LLC

Hello! Using PxPlus 2022 & iNomads 19.1. Does the Auto Refresh panel setting not work in iNomads? Tests that I've done suggest it does not. I was hoping to avoid adding Refresh_Flg=1 in multiple routines. But with just Auto Refresh on, when a routine completes and I'm back on the panel in iNomads, certain objects were e.g. staying displayed/hidden when the routine was supposed to have done the opposite, or multilines had values displaying even though the routine cleared them.

I appreciate whatever feedback there might be.

Paula McKeever
CAI Software

Hello. This is a follow-up to an earlier ticket posted by someone about the same issue, but I didn't see a resolution there. Here's the link: https://forum1.pvxplus.com/index.php?topic=1001.msg3412#msg3412

I'm experiencing basically the same issue. When I hop from my IT editor to another window and then return, the loaded code is listed starting above the top boundary of the defined code area. Note: not every time, only some of the time. See attached screenshot.

Like the other user, this started after an upgrade. (In our case, we leapfrogged from 17 to 19.) We also have BX emulation on.
But unlike the other user, who used dark display, I use light.
We run PxP on a direct RDP session to our Win 2022 development server.
I want to reiterate: this is new behavior, in effect as of the new PxP version.

TIA.

Paula McKeever
CAI Software LLC

Thanks James. 'RI' did the trick, although we haven't decided about using it yet, since we don't want the behavior to be used elsewhere, and we might not want to risk turning it on in the pgm and then aborting out before turning it back off. But we are considering it! Thanks again.

Paula McKeever
CAI Software LLC

I neglected to mention that I cannot convert the data to string prior to loading the grid. It needs to be numeric so that it gets exported as numeric data to a spreadsheet.

Using PxP 2022. My question concerns formatting of data in numeric cells in a grid. In Format Definition, I assign a numeric variable name to my column; e.g. Cost. In my supporting program, I set the cost's format mask with

let detail_box.ctl'Column$="Cost",detail_box.ctl'row=0, detail_box.ctl'cellformat$="######0.00-"

In the PxP documentation, the CellFormat property redirects to the documentation about multi-line Fmt$ property, which says "Before being output, the number is rounded to the number of decimal places specified in the format mask." But when I test, it truncates, not rounds. (By the way, the incoming value does not exceed the mask.)

Is there a correct way of having numeric grid cell data round instead of truncate?

Thanks in advance.

Paula McKeever
CAI Software LLC

Aha. Eureka! Thanks Len!

(I wasn't sure how to word the subject line) 

In the IT editor, if I go to a particular line -- let's say the first line in a routine/method -- is there a way to have the line load at the top of the display? The line in question loads partway down the screen, and I often have to scroll down to see the entirety of a routine that I might not need to if that first line appeared at the top. (By the way, we use line numbers in our installation.)

Just wondering if there's a way, for efficiency's sake. Thanks in advance!

Paula McKeever
CAI Software LLC

That does indeed help, Stéphane. Thank you!

First time experiencing a Win 2022 server. Have PxPlus 2022 installed. The built-in Language Help (via the Help menu) does not display content on the right panel?
Might that be an issue with the 64-bit OS not playing nice with the HTML Help version? Or other?

Thanks in advance.

Paula McKeever
CAI Software

Greetings. The Data Dictionary Update pgm *dict/dd_updt: it looks as though it returns error descriptions, not error numbers. If one's code happens to call it, will checking the err variable immediately upon returning from the call contain the error number associated with the returned message?

Thanks in advance.

Paula McKeever
CAI Software LLC

We've just discovered in the documentation for [ODB] open that the open can have parameters, including CHECK_NUMERICS. (Y/N) That seems to enforce the decimal check on the write. We're going to explore this further.

Still a little fuzzy about the "Force Data Validation on Write/Update" checkbox in DD Maint; not only does the test of the first number (e.g. the "8" in 8.2) seem to include the decimal point in the count, but that first number is for the digits to the left of and including the decimal point, not the total number of digits in the entire number (scale included, decimal point excluded) like for a write to SQL. If I understand correctly, a valid max for an 8.2 is

"Force Data Validation on Write/Update": 1234567.12
[ODB] write to SQL with CHECK_NUMERICS on: 123456.12


Paula McKeever
CAI Software