Ok, back at it again and the problem continues with a new variation.
/// here’s the procedure
;fileglobal fgConcChoice
;fgConcChoice=“999:Test”
fgProgress=""
fgProgress=fgConcChoice showvariables fgProgress ; formulaTest1
displaydata fgProgress
fgProgress=array(fgConcChoice,2,":") showvariables fgProgress ; formulaTest2
displaydata fgProgress
stop
///
Commenting out the fileglobal definition for the purposes testing the popup menu.
The popup menu is set to “formula” the formula is a variable created by an arrayselectedbuild which creates a cr() separated list in the form of “IdNum:ItemName”. The first line is NOT empty.
One item chosen at a time, many different choices tried.
Have added displaydata instead of relying on the TDO.
Selecting an item at random from the popup,(“655:Goobers Small”) the first text display window shows “655:Goobers” and the second displays blank.
If I switch the first statement (formulaTest1) and the second statement (formulaTest2) the first displaydata window shows “Goobers Small” and the second displays blank.
This is basically where I was at the first post.
If I comment out “showvariables fgProgress” (with “;”) from both statements, then the results are as expected, ie: 655:Goobers followed by Goobers Small.
BUT…if I go back and remove the “;” so “showvariables fgProgress” is back in, then it runs as expected, second displaydata is no longer blank.
BUT…remembering the problem went away after a power failure, I quit and restarted PanX. And the problem returns.
Comment out “showvariables fgProgress”, all works right.
Un-comment them in, all works right.
Is there some sort of variable I could be creating elsewhere that is clashing? I use fgProgress alot. I tried changing it to fgProgressx but got the same results.
Also tried changing to popup to a CSV with some test data typed in, same results.
As for the final clue, you can see commented out above, I tried defining fgConcChoice without the popup menu. When I run the procedure without the popup, it works correctly every time. Switch back to the popup and the problem returns.
FWIW: using // instead of ; produces the same results.
This is all on my home mac using El Capitain. I have not tried it on my work Mac with High Sierra.