Kbase P107536: Why does the NO-FOCUS attribute cause the border to be removed from a button which also has the DEFA
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/08/2005 |
|
Status: Unverified
GOAL:
Why does the NO-FOCUS attribute cause the border to be removed from a button which also has the DEFAULT-BUTTON attribute set to true?
FIX:
The NO-FOCUS attribute implies that a button does not get physical or implied focus. When the DEFAULT-BUTTON attribute is set to true the button is painted with a small border around it to visually show that it has an implied focus (i.e. when you press the enter or return keys they do not get sent to the currently focused widget, instead they get sent to the default button). Turning on the NO-FOCUS attribute removes the border because the border implies visually that the widget can get focus (which is in conflict with the NO-FOCUS attribute).
The NO-FOCUS attribute is designed for use with buttons which will never have any kind of focus (i.e. buttons used as a toolbar) and consequently should not be used in combination with the DEFAULT-BUTTON attribute.