Command-keys for Scripts

[Brian C.]

Writing these up as a single feature request, and we'll look into 
including it in a later release. In general, we lean towards having a 
nice GUI for assigning a key command to a script/menu item/whatever, 
but that would be a ways off, at this point. I guess what I'm trying to 
say is that assigning key commands to scripts is more likely to show up 
in the app in some form; it's less likely that it'll be this particular 
implementation of that feature.

Dan: how does the situation where the user has attempted to map a key 
command to a script, but the application already uses that key command. 
Presumably, the script is just out of luck, but I'm wondering if 
there's any feedback to the user. Additionally, what apps use this 
method, so I can take a look at 'em?

Sincerely,

Brian C.
Support Manager
Omni Group


On Tuesday, August 13, 2002, at 12:02  PM, 
omnioutliner-users-request at omnigroup.com wrote:

> Send OmniOutliner-Users mailing list submissions to
> 	omnioutliner-users at omnigroup.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://www.omnigroup.com/mailman/listinfo/omnioutliner-users
> or, via email, send a message with subject or body 'help' to
> 	omnioutliner-users-request at omnigroup.com
>
> You can reach the person managing the list at
> 	omnioutliner-users-admin at omnigroup.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of OmniOutliner-Users digest..."
>
>
> Today's Topics:
>
>    1. Another Feature Request: Command-keys for Scripts (Mark Guzdial)
>    2. Re: Another Feature Request: Command-keys for Scripts (Dan 
> Frakes)
>
> --__--__--
>
> Message: 1
> Date: Tue, 13 Aug 2002 09:33:49 -0400
> Subject: Another Feature Request: Command-keys for Scripts
> Cc: omnioutliner-users at omnigroup.com
> To: "Brian C." <dvorak at omnigroup.com>
> From: Mark Guzdial <guzdial at cc.gatech.edu>
>
> Here's another feature request, but fairly low-priority (and probably
> pretty difficult): I'd like to be able to assign unassigned 
> command-keys
> to scripts.  For example, I have a "Save All" script that saves all my
> open windows.  I'd like to be able to do that with (say) 
> Command-Shift-S.
>
> The "fairly complicated" part is not technical but interface wise.  
> It's
> hard to come up with a nice interface that makes it obvious what you're
> doing in assigning command keys, and then there's the issue of the
> script being moved out of the Scripts folder after you've assigned the
> key and how you deal with that and what novices are supposed to make of
> it, etc.  (I wouldn't mind some kind of naming convention, e.g., I name
> my script "Save All--CmdShS".)
>
> Despite the problems, it's on my "Dear Santa," er, "Dear Brian" list 
> :-)
>
> Mark
>
> On Sunday, August 11, 2002, at 02:38  PM, Brian C. wrote:
>
>> These are both fairly common feature requests, and we plan to tackle
>> them at some point. We don't have room in our schedule right now, but
>> we do want to add these features in a future version of OmniOutliner.
>>
>> If you have any other questions or suggestions, please don't hesitate
>> to contact me. When replying, please include the quoted text of this
>> message. We really appreciate your help!
>>
>> Sincerely,
>>
>> Brian C.
>> Support Manager
>> Omni Group
>>
>>
>
>
> --__--__--
>
> Message: 2
> Date: Tue, 13 Aug 2002 10:39:47 -0700
> From: Dan Frakes <lists at informinit.com>
> Subject: Re: Another Feature Request: Command-keys for Scripts
> To: omnioutliner-users at omnigroup.com
>
> On 8/13/02 6:33 AM, "Mark Guzdial" <guzdial at cc.gatech.edu> wrote:
>> Here's another feature request, but fairly low-priority (and probably
>> pretty difficult): I'd like to be able to assign unassigned 
>> command-keys
>> to scripts.  For example, I have a "Save All" script that saves all my
>> open windows.  I'd like to be able to do that with (say) 
>> Command-Shift-S.
>>
>> The "fairly complicated" part is not technical but interface wise.  
>> It's
>> hard to come up with a nice interface that makes it obvious what 
>> you're
>> doing in assigning command keys, and then there's the issue of the
>> script being moved out of the Scripts folder after you've assigned the
>> key and how you deal with that and what novices are supposed to make 
>> of
>> it, etc.  (I wouldn't mind some kind of naming convention, e.g., I 
>> name
>> my script "Save All--CmdShS".)
>
> There is actually a fairly "standard" way of doing this that has been
> adopted by many other applications that feature a script menu. You 
> simply
> place the character \ at the end of the script name, then follow it 
> with a
> combination of the following modifiers and any other key(s) on the 
> keyboard:
>
> o = option
> c = control
> m = command
> s = shift
>
> The application sees everything after the \ as they key combination 
> used to
> run that script.
>
> For example, I have a Microsoft Entourage script that files messages in
> folders called "File Msgs in Folder\coF" -- I simply hit 
> command-option-f to
> automatically run it.
>
> I agree that being able to assign key combos to scripts would be a 
> great
> feature, and I encourage the use of the above method for keyboard 
> control of
> them.
>
>
>
> --__--__--
>
> _______________________________________________
> OmniOutliner-Users mailing list
> OmniOutliner-Users at omnigroup.com
> http://www.omnigroup.com/mailman/listinfo/omnioutliner-users
>
>
> End of OmniOutliner-Users Digest