On 11/17/00 1:13 PM, "Allen Watson" <[EMAIL PROTECTED]> wrote:
> On or near 11/17/00 10:17 AM, Paul Berkowitz at [EMAIL PROTECTED]
> observed:
>
>> OK, I've discovered why control-C but NOT control-command-C opens things in
>> Entourage and everywhere else, whereas for Allen control-command-C works the
>> same as control-C.
>>
>> I have control-command-C defined as my "hot key" for showing/hiding the
>> control strip, so that is what it's doing when I press control-command-C in
>> any app. It evidently overrides anything else without problem. I'm not sure
>> if that's the default or if I set it that way.
>
> Do you intend to say that when you change or disable the control strip hot
> key, then you also see Cmd-Control-C opening things in Entourage? In other
> words, can we conclude that this behavior is present for everyone unless
> they have something that intercepts the keystrokes first? And that,
> therefore, for script shortcuts or OneClick shortcuts, we should avoid
> Cmd-Control combos?
No. I use a lot of control-command combos for my scripts, since Entourage
has so many option-command combos already built in for various features. I
was just suggesting that whereas command-C seems to usurp control-command-C
if you have nothing else specifically assigned to control-command-C (which
is, in itself, quite odd since other combos I know don't "ignore" modifier
keys: adding a modifier key usually denies any partial combo of the various
keys held down), having something specifically assigned to
control-command-C, or at least the system-wide Apple-implemented hot key for
the control strip, at least, prevents any usurpation.
Allen, you may recall that I discovered a few weeks ago that your problem
with one of my scripts being run from a schedule which kept opening to the
"initiation" routine of my script (set to happen when only the "command" key
was held down), is due to the fact that all of us commonly depress one key
in a combo before we press the others down. Or maybe you didn't realize
that. So that if you happened to be holding down just the command key,
preparatory, say, to adding an "S" or an "O", just when the schedule was
running, you would get the script initiation routine. (In that particular
case I have changed the key combo to command-option-control to make sure
that it doesn't happen by accident. I do this now for all my scripts which
will be run by schedule.)
I think, if you try to observe yourself, that you may find frequently
depress the control and letter keys before you add the command key, even if
for just a split second. Is that possible?
--
Paul Berkowitz
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
To search the archives:
<http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>
