Newbie - Button values, shortcut key, response and indicators

[charles.wilt]

Hello,

New to Profound, plenty of RPGLE experience and some Windows & Web GUI experience. Dealing with 5250 screens converted to Rich UI screens.

Looking to confirm my understanding of how profound interacts with indicators / AID byte.

From what I've found in the forum, a button's
1) "response" property controls which named indicator or *INxx indicator gets flipped when the button is pressed.
2) "shortcut key" property controls which *INKx indicator gets flipped and the value of the AID byte

Correct?

Now, a question about the text on a button. In designer, I see the value property of various buttons as
[Ok]
[Exit]
F6
[Cancel]

When I run the program, I see the following text
Ok
Exit
Add
Cancel

So two questions
1) Where did the Add text come from? It's not in the DDS source anywhere.
2) What's the significance of the [brackets]?

Thanks!
Charles Wilt

[Scott Klement]

Hello Newbie!

Your assessment of the response and AID key values sounds right. I would add that the AID key stuff is really only for backward compatibility with old, converted, applications -- we do not recommend using AID keys in new applications. When a shortcut key is pressed, it will also turn on the response indicator, and we recommend using named response indicators in new applications. Programs should use the response indicators rather than old 5250 stuff like AID keys or *INKx indicators.

With regards to the text on a button, you aren't providing complete information. The brackets could mean any of these things:

1) The field has text containing brackets in it.
2) The field is bound to a field. Clicking the binding button (little yellow/white puzzle piece) will provide more information.
3) The field is using the language translation feature. Clicking the translation button (little globe) will provide more information.

In converted applications, it's also possible that the text is set by a script. For example, in 5250 applications, the text that's printed on the display that says something like "F3=Exit" is just text, and separate code with something like "CA03" indicates whether the function key is available, but in Profound UI, the availability and text are both part of the same thing -- a button. For that reason, when something is converted, we often use a script to allow the name of the button to be set to something different depending on a condition, since you can't otherwise condition the text of a button without also conditioning the button itself.

I would suggest that you ask someone at Dealertrack to teach you how Profound UI works. It is a bit hard, and very time consuming, to teach basics in a forum post. If noone at Dealertrack is able to do this, Profound Logic can offer you onsite training with one of our instructors for a fee. Contact our sales department if you'd like a quote or to arrange this.
http://www.profoundlogic.com/contact?ty ... FOUND%20UI