>Alain: How about dialogs that must appear to the user
>when he does it manually, but which we don't want to
>display when this same action is taken by a script?
Alain,
either they'll be using the "without dialog" qualifier which will turn
this off, or if it's a new feature we'll have a handler or command that
does this. If we hard-wire the option key it'll be in the way in cases like
the ones I described before. It just *can't* be part of the answer command
as answer might be used for lots of dialogs.
>Alain: Why are you insisting so strenuously that it
>must not be hard-coded?
See above. I have no problem with FreeUI's dialogs having this feature.
>Alain: I suggest some optional syntax and/or some new
>properties :
>
>1. lock dialogs
>
> -- similar to existing "lock error dialogs"
>
>2. set lockDialogs to true
>
> -- similar to existing "set lockScreen to true "
>
>3. doMenu menuItem [with/without dialog] [with keys]
Alain, later. If there's a need for this, we can add it if we don't find a
better solution. For now let's focus on HC 2.x's feature set.
Cheers,
-- M. Uli Kusterer
------------------------------------------------------------
http://www.weblayout.com/witness
'The Witnesses of TeachText are everywhere...'
--- HELP SAVE HYPERCARD: ---
Details at: http://www.hyperactivesw.com/SaveHC.html
Sign: http://www.giguere.uqam.ca/petition/hcpetition.html
