Profound Logic Forums

The DDS conversion seems to ignore the VLDCMDKEY keyword? Are there plans to support it?

Support for this keyword will be available with version 2.1.4, which we plan to publish early next week.

I have installed 2.1.4 and I see the valid command key property in the screen properties in the designer, but the named indicator is not being set *on in may RPG program when a function key is pressed.

Do I need to make a configuration change to the function key buttons that the DDS conversion creates?

Was the display file reconverted after installing 2.1.4?

Yes, the DSPF was reconverted after installing 2.1.4.

When looking at the display with the visual designer I can see in the screen properties for the subfile control record format that *IN26 is bound to "Valid Command Key" property. The is also code in the compile listing to set *in26 after the write.

puiHandler(QrnOpenAccess_T);
If QrnOpenAccess_T.rpgStatus <> 0;
PUIRunError('RNX' + %Char(QrnOpenAccess_T.rpgStatus):'KUN018':
'WRITE');
EndIf;
*IN01 = ind_KUN018.In_____01;
*IN03 = ind_KUN018.In_____03;
*IN12 = ind_KUN018.In_____12;
*IN26 = ind_KUN018.In_____26;

However, when I debug the job after pressing a function key (e.g. F12) ind_KUN018.In____26 is zero.

Which browser did you use to convert the file? We have identified a problem with Google Chrome where the iteration order of JavaScript object properties does not match the insertion order.

This has a side effect of creating the "valid command key" indicator as an output indicator rather than a response indicator, and the value can never be set.

We are working on a Chrome workaround for the next release. In the mean time, can you try reconverting or just opening and resaving the display file with another browser like Internet Explorer or Firefox?

Problem solved. I'm using Firefox, but it seems that the browser was caching the javascript from 2.1.3. I cleared the cache and reconverted the DSPF the screen now functions properly. thanks.