Le 29 sept. 08 à 19:51 (soir), Terry Ford a écrit:
In this case it would be to cancel the encryption as the message is
a confirmation of an action that the user has already chosen. In
other words, it agrees with the message.
The "other words" part is the most helpful one ;-) (really)
The standard way to cancel any process is to select the Cancel
key or its Shortcut equivalent. For this reason, the Cancel key
should really not be used as a selected option and simply be used
as an abort of the entire process.
... Hmm... I'm reading your sentence 3 times... I still cannot
understand it fully (sorry). What do you mean by "a selected option"?
Your selected options are "Don't Encrypt" or "Encrypt". Any button
that says "Cancel" should abort both of these options and go back
to the calling source.
My application has no "calling source". It just treats files dropped
into it (like Stuffit Expander or... winzip, I think).
The shortcuts can be disabled and the LR has the following statement.
"Only one button can be the Cancel button. Some operating systems
do not allow one button to be both the Cancel and Default buttons."
Besides not identifying which OS, it also is confusing as I think
it really means that, on Mac OSX, you cannot have the same button
respond to the Escape key, Command-Period keys, Return key or Enter
keys. There is a lot of flexibility in the MessageDialog class but
it does have it's limitations.
As far as I know, it's win32 (perhaps also linux) which does not
allow the same button to be the default and cancel.
But I agree about the confusing documentation.
In a MessageDialog with only an action button and an
AlternateButton, there is a button at the right side of the dialog
and the other one at the left side, with a blank space in the
middle. It does not seems esthetic.
But I can resolve this by using the Cancel button, and setting the
CancelButton.Cancel property to false.
Correct. And you could set the Caption of the Cancel Button to be
"Encrypt".
Well, not "Encrypt" but "Continue encryption" as it can have already
been started.
You will still have to handle the user's response in your code.
Done ;-)
Programming is not so hard, it's more the way to present things that
is hard for me (sometimes).
The whole point is that Yes and No are very ambiguous in this
Negative Logic type of situation whereas Don't Encrypt and Encrypt
are very specific.
Yes... I think the "Yes"/"no" in my original question was just an
example... I hope so...
I'm not sure about Windows but on Mac there must be at least one
default key in the Message Dialog class.
Indeed. I know exactly like you here.
Well, I just tested it in XP and it is exactly the same as OSX.
There MUST be at least one default button.
Ok... didn't assumed so...
If there were only some way to get those icons with the Caution and
App icon from within Rb for our own custom dialog windows I would
be very happy. That would make them appear normal in OSX at least.
It's also only the GraphicsCaution icon that is a problem but, I
guess, not really significant in this RS Windows oriented world. :P
Yes, I couldn't agree more...
But Graphics.DrawCautionIcon does not work for you?
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
|