[Rwp] OSARA key map

Mon Feb 23 14:55:19 EST 2015

Ah, but you see, it does.
Try mapping a key to an action, and you'll see a dialog letting you know 
the current asignment, and asking you if you want to overright.

On 2/23/2015 2:15 PM, Brandon Keith Biggs via RWP wrote:
> Hello,
> In many programs that blind people come in contact with, k, or ctrl+k, 
> set bookmarks, so having k makes perfect sense.
>
> But frankly, having a tried and tested key map with documented 
> keystrokes is all we need. I will change your keymap sometime, so who 
> cares how it begins?
> I would like to have some way to figure out if a keystroke has already 
> been taken. From what I remember when looking at Reaper's keymapping 
> functions, there were hundreds of actions. A key stroke does not 
> always trigger when you press it (it may be in the wrong area) and if 
> it does trigger, there is no way to know what it does if it doesn't say.
> Audacity has a lovely feature that will keep you from over-riding a 
> current key-stroke and it will tell you where that key-stroke is 
> currently.
> But this is almost getting into something Reaper should do and not an 
> accessibility plugin.
> Thanks,
>
> Brandon Keith Biggs <http://www.brandonkeithbiggs.com/>
> On 2/23/2015 7:11 PM, Derek Lane via RWP wrote:
>> This eliminates the logical key to asign a marker.
>> ok, m?  we'll go with the second letter, a?  oh wait, that's to arm a 
>> track.
>> No problem, r then?  oh wait, no.  That's record, k perhaps?
>> Sure, k to put down a time marker.
>> If we're going to make reaper something that beginners can learn, I 
>> feel that simplifying the keymap won't work, but having 1 keymap the 
>> majority agrees with would allow those good at documentation to do 
>> there thing.
>>
>>
>>
>>
>>
>> ----- Original Message ----- From: "Scott Chesworth via RWP" 
>> <rwp at bluegrasspals.com>
>> To: "Reapers Without Peepers" <rwp at bluegrasspals.com>
>> Sent: Monday, February 23, 2015 4:59 AM
>> Subject: Re: [Rwp] OSARA key map
>>
>>
>>> Hi Brandon,
>>>
>>> I'm curious about something. Taking mute as an example, why would you
>>> want M and Shift+M to mute and unmute, when just M could act as a
>>> toggle, so one press mutes, the next press unmutes. My thinking is
>>> that if it's a toggle, it then frees up Shift+M to be used for
>>> something related to muting that applies to a wider range of tracks,
>>> but what's yours?
>>>
>>> Cheers
>>>
>>> Scott
>>>
>>>
>>> On 2/23/15, Brandon Keith Biggs via RWP <rwp at bluegrasspals.com> wrote:
>>>> Hello,
>>>> I agree, build the keymap for the newbies and not for the power users.
>>>> a and shift+a for arm and un arm, s + shift s for solo and unsolo, m +
>>>> shift s for mute and un mute and the right and left arrow keys for
>>>> moving forward and back in the key map.
>>>> Thanks,
>>>>
>>>> Brandon Keith Biggs <http://www.brandonkeithbiggs.com/>
>>>> On 2/23/2015 3:28 AM, Scott Chesworth via RWP wrote:
>>>>> Hey Jamie,
>>>>>
>>>>> Wouldn't worry about overwriting the default bindings. because it's
>>>>> widely acknowledged that they suck anyway. There are tons of forum
>>>>> threads about it. It seems like one of the first things sighted 
>>>>> Reaper
>>>>> users do once they start trying to improve upon their productivity is
>>>>> build their own keymap. I haven't yet heard of a case where such a
>>>>> sighted power user transitions over to using Reaper with a screen
>>>>> reader and starts screaming blue murder about their keymap being
>>>>> munched.
>>>>>
>>>>> Personally, I'd vote we hash out a keymap on here however the heck
>>>>> that could be done productively and work toward that automated
>>>>> install. That way, if anybody has a little more work to do, it's the
>>>>> power users instead of the people picking Reaper up for the first
>>>>> time. Smoother entry for the newbies, and less support.
>>>>>
>>>>> Scott
>>>>>
>>>>> On 2/22/15, James Teh via RWP <rwp at bluegrasspals.com> wrote:
>>>>>> On 23/02/2015 8:19 AM, adriandavids404--- via RWP wrote:
>>>>>>> I stand to be corrected, but I do think Reaaccess does allow the 
>>>>>>> user
>>>>>>> to
>>>>>>> choose if the Reaaccess key map should override the user's key map?
>>>>>> My apologies for being unclear. You're correct; it does. What I 
>>>>>> meant is
>>>>>> that (assuming I'm not incorrect) you have two options: override the
>>>>>> keymap *completely* or don't install it at all. That is, if 
>>>>>> you've made
>>>>>> changes before installing it, you can't keep those changes while 
>>>>>> also
>>>>>> installing the ReaAccess keymap.
>>>>>>
>>>>>> Jamie
>>>>>>
>>>>>> -- 
>>>>>> James Teh
>>>>>> Email/MSN Messenger/Jabber: jamie at jantrid.net
>>>>>> Web site: http://www.jantrid.net/
>>>>>> Twitter: jcsteh
>>>>>>
>>>>>> _______________________________________________
>>>>>> RWP mailing list
>>>>>> RWP at bluegrasspals.com
>>>>>> http://bluegrasspals.com/mailman/listinfo/rwp
>>>>>>
>>>>> _______________________________________________
>>>>> RWP mailing list
>>>>> RWP at bluegrasspals.com
>>>>> http://bluegrasspals.com/mailman/listinfo/rwp
>>>>
>>>>
>>> _______________________________________________
>>> RWP mailing list
>>> RWP at bluegrasspals.com
>>> http://bluegrasspals.com/mailman/listinfo/rwp
>>>
>>
>> _______________________________________________
>> RWP mailing list
>> RWP at bluegrasspals.com
>> http://bluegrasspals.com/mailman/listinfo/rwp
>
>
>
> _______________________________________________
> RWP mailing list
> RWP at bluegrasspals.com
> http://bluegrasspals.com/mailman/listinfo/rwp

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://bluegrasspals.com/pipermail/rwp/attachments/20150223/e29f0a29/attachment-0001.html>