
These values correspond to the notice’s status. The notice status contains the value of the but-
ton that was selected on the notice. The location where the status is stored can be set with the
attribute NOTICE_STATUS. If NOTICE_STATUS is not set, the notice status can still be
obtained by using xv_get() on NOTICE_STATUS. If the attributes NOTICE_BUTTON_YES
and NOTICE_BUTTON_NO are used, the notice status is either set to NOTICE_YES or
NOTICE_NO, depending upon the user’s notice button selection, which causes the notice to
pop-down. As shown in simple_notice.c, the strings associated with the “Yes” and “No” but-
tons are set with the attributes NOTICE_BUTTON_YES and NOTICE_BUTTON_NO. The notice
button created with NOTICE_BUTTON_YES is the default button and will have the OPEN LOOK
default ring around it.
The notice choices listed above also respond to accelerator keys. In other words, in addition
to the RETURN key, whatever key that is mapped to the semantic action
ACTION_DEFAULT_ACTION can also be used to select the NOTICE_BUTTON_YES button. The
key that is mapped to the semantic action ACTION_STOP can be used to select the
NOTICE_BUTTON_NO button.
When the notice window is mapped, the cursor is immediately warped (moved) to the default
button since it is the default response of the notice.
It is quite common for the application to have more than one appropriate response to some
kind of notice ...