Class: UserConfirmation

• Inheritance
• Description
• Related information
• Instance protocol
  • accessing
  • default actions
  • queries

Inheritance:

   Object
   |
   +--GenericException
      |
      +--Notification
         |
         +--UserConfirmation
            |
            +--ProvideAnswerNotification

Package:

stx:libbasic

Category:

Kernel-Exceptions-Notifications

Version:

rev: 1.9 date: 2016/06/03 12:16:11

user: sr

file: UserConfirmation.st directory: libbasic

module: stx stc-classLibrary: libbasic

Author:

Stefan Vogel

Claus Gittinger

Description:

This confirmation query is used when a user confirmation is required
somewhere within a model's operation (i.e. in non-GUI code).
Instead of directly asking via Dialog confirm... messages,
this should be raised.
Its default behavior is the same as the above dialog.
However, the query can be caught and answered by an exceoptn (a query-) handler,
to suppress these GUI interactions in situations, where they are not wanted.

This is a much better approach to the alternatives:
    passing additional 'doConfirm' arguments down from the high level caller
    keeping the doConfirm settings in a passed down flag object
    keeping the flag in a global (very bad)
    keeping it in a class var (almost as bad)

Notice: that's one of the nice consequences of proceedable exceptions.

Related information:

    Query
    Notification
    Exception

Instance protocol:

 aspect

the aspect the user is asked. Set this to a symbol.
It can be used by a exception handler

 aspect: aSymbol

the aspect the user is asked. Set this to a symbol.
It can be used by a exception handler

 canCancel

answer true, if the user is allowed to press the cancel button
in a confirmation dialog

 canCancel: something

 defaultAnswer

used to pass information from the raiser to the GUI dialog.
Specifies, which answer of the three (yes/no/cancel) should be the return-key-default.
If not specified, the cancel-key will be the default

 defaultAnswer: aBooleanOrNil

used to pass information from the raiser to the GUI dialog.
Specifies, which answer of the three (yes/no/cancel) should be the return-key-default.
If not specified, the cancel-key will be the default

 defaultAction

Default action for confirmations: open a info box with description.
If no GUI present, assume that the user pressed 'yes'

 askingContext

return the context which did the confirm-request