Has anyone that uses Nomads heavily started upgrading their user base to the new version 18 yet?
We have slowly started rolling out to our users and have noticed a couple of minor problems.
The first we can work around, but I thought i'd note it down here in case it was a bug that PxPlus wasn't aware of. The _QLST_DEF$[X,0] variables are now no longer populated with the original list box format when a panel is drawn (although the array is still defined). We were using this variable where a list box format is defined in nomads but then logic in our program alters the list box logic to add/remove/shrink/grow columns as required. We are working around this by setting the variable when the panel is first opened, or by reading the format out of the nomads library file. Not ideal but we can work around it.
The second is a strange issue that is seemingly randomly occurring since updating users to V18. We appear to have the word 'BLACK' being placed in string variables we are using to hold prices. These string variables and linked to multi lines on our nomads panels. I know prices should probably be stored in numeric variables but the string variables allow us to format the price as we see fit, allow our users to enter formulas etc in the pricing fields, and we just convert string variables to numeric variables when we need to perform calculations. We obviously have traps to ensure users can't enter letters in these sorts of fields, and yet somehow 'BLACK' is appearing in those variables and causing an error 26 in calculations. It is either the variable that is getting corrupt, or the multi line that is being populated with the value which is updating the variable but without triggering the on change logic (as if it was, the variable would be set back to "" and would return the user to the field to 'try again'.)
It's occurred three times this week in two different version 18 installations.
Error dump of error #1:
Error dump of error #2:
And the same for #3:
I can assure you that our code is not setting the word 'BLACK' anywhere! So far, I've yet to be able to replicate the issue on demand which makes it really hard to trace.
A couple of things to note.
1. We do use visual classes on all our controls, not sure if the problem is coming from there given that black is the default text colour.
2. All our cost and price fields are validated and formatted by a global function. (see below)
LET PRICE$=FN%PRCENT$(PRICE$,TAXRATE,%SELLPMASK$); IF PRICE$="ERR" THEN LET PRICE$="",NEXT_ID=PRICE.CTL; RETURN
Our global functions haven't changed between versions 16 and 18 of PxPLus but maybe its possible that somehow the data being passed back from the function is getting corrupt?
Anyone else having any issues like this with the new version?