It defines the behavior when a mouse click or accelerator key activates for example a PushButton object and at the same time moves the keyboard focus away from an EditText or ComboBox object.

In this situation, the program should be notified about both the EditText or ComboBox and the PushButton event.

If the ruleoverride attribute value is zero, first the EditText or ComboBox rule is submitted to the program, along with the path of the EditText or ComboBox object.

The PushButton rule value is saved to be submitted immediately on the next DLG DO invocation, along with the path of the PushButton object, except if a DLG SET .focus is executed in between these two DLG DO invocations.

If the ruleoverride attribute value is nonzero, only the PushButton rule is submitted, along with the path of the EditText or ComboBox object. This way, both rule submissions are combined into a single submission.

Note: A special behavior is defined if a non-focusable object is clicked or activated with an accelerator key. A non-focusable object is an Image object or any object located in a ToolBar.

Activating a non-focusable object never moves the keyboard focus away from an EditText or ComboBox object, therefore only one rule submission takes place, in the example above with the PushButton rule value.

If the ruleoverride attribute value of the non-focusable object is zero, this submission uses the path of the PushButton object, if nonzero, it uses the path of the EditText or ComboBox object.

The object classes providing the ruleoverride attribute are:

CheckBox		default ruleoverride value = 0
Image		default ruleoverride value = 1		(never focusable)
ListBox		default ruleoverride value = 0
PushButton		default ruleoverride value = 1
RadioButton		default ruleoverride value = 0
TabBox		default ruleoverride value = 0
Tree		default ruleoverride value = 0