ASNA WingsRPG™ Reference Manual

Enabled Function Keys

The wide array of function keys available on an IBM i interface provides a lot of flexibility and functionality to IBM i programs, but hardware differences have traditionally made it impossible to bring them smoothly into the Windows world. Wings solves this problem by providing an on-screen button that corresponds to each enabled function key. Each button is a DdsButton Control.


Function Keys are coded into Wings pages with the following format:

<mdf:DdsButton id="ddsFuncKey" runat="server" AidKey="Func" Text="Func Key" />

By default these buttons appear in a row (or set of rows) near the top of the Wings page, and have the names of the F-Keys they mimic. Clicking the button will cause the program on the IBM i to respond just as if the F-Key had been pressed.

Warning – If you're adding new function keys it's vital to add the keys to be implemented to the FuncKeys property of the DdsRecord Control where they'll be used. To activate a new Function key on a record, add the text Fx 0x (with x being the number of the function key) to the FuncKey property in either the Properties Window or the HTML for the control. Wings Validation.

The labels of the function key buttons can easily be changed, as can their shapes, sizes, and location, with modifications to the properties of the DdsButton control that represents them. The Function (or Attention) key to associate with a DdsButton is set with the AidKey property. This can be done by setting it through the Properties Window for that button, or in the HTML by adding AidKey="Fx" to the button's properties. For a look at how to make some specific changes, see the topic on changing the placement of function keys.