[Rwp] OSARA keymap

[Nick Giannak]

Jamie,
On 2/22/2015 4:47 PM, James Teh via RWP wrote:
> 1. Can we do better? Does anyone have an idea as to how we can assign 
> these actions to maximise efficiency and intuitive experience without 
> making other things less functional? I'm not normally a fan of 
> overriding built-in bindings, but we're already doing that for track 
> navigation anyway (given the default bindings are just silly), so 
> perhaps this is just something we need ot accept for the sake of a 
> good user experience.
     I can't honestly see how, especially given that keymaps like that 
have become expected behavior not only in Reaper, but in products like 
CakeTalking as well. I could be wrong here, but to me, that keymap was 
utterly logical, much as buttons on a console are.
> 2. Am I seriously the only one who has an issue with the use of 
> function keys for this purpose? If so, I guess I can consider 
> conceding the point and just maintaining my own separate keymap.
     I'd be shocked if you weren't the only one, honestly. Considering 
what kind of contention points there have been for this, I really would 
be very surprised. Add my name to the keep the function keys list.
> 4. As I understand it, the way ReaAcccess installs the keymap is to 
> simply override the user's existing keymap completely. This isn't 
> ideal, but it does allow for automated installation. The alternative 
> is to provide a keymap the user must import. Have there ever been 
> complaints from users about this keymap overriding or do people tend 
> to just accept this is what happens? I guess this is okay for most, 
> since they're probably new REAPER users.
     Never have I ever considered it a problem, especially given that 
Reaper prints the keymap to an hTML file whenever one wants it.
Thanks,
Nick