The important part of this thread though is that you should be careful
how you test the return from message dialogs. The rule of thumb that
we use is if you're going to do something with one of the possible
responses then that is the one you should test. So if you're asking
the user if they really want to delete something then you abort on
anything other than 'Yes'. If on the other hand you ask them if they
want to keep the record, then you abort on anything other than 'No'.
"Robert Martin" <[EMAIL PROTECTED]> wrote on 21/06/2001 10:20:19:
>
>I tend to agree with Rohit from a usability stand point. we often use
>OK and Cancel instead of yes/ no.
<snip>
>----- Original Message -----
>From: "Rohit Gupta" <[EMAIL PROTECTED]>
<snip>
>> Steve,
>>
>> I think all those boxes should have yes/no/cancel buttons even if
>> cancel does the same as no. :-)
I've always thought that this is only useful if all the buttons do
different things. Like a save query that pops up when you close a file
- yes to save, no to discard changes, and cancel to keep the file open.
Redundant GUI elements just aren't sexy :>
PS: Sorry Rob, my email client went nuts and sent this to you (possibly
twice) instead of the list. Oops.
--
Corey Murtagh
The Electric Monk
"Quidquid latine dictum sit, altum viditur!"
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
To UnSub, send email to: [EMAIL PROTECTED]
with body of "unsubscribe delphi"
