<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Ah, but you see, it does.<br>
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.<br>
<br>
<br>
<br>
<br>
On 2/23/2015 2:15 PM, Brandon Keith Biggs via RWP wrote:<br>
</div>
<blockquote cite="mid:54EB7C34.6000204@gmail.com" type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<div class="moz-cite-prefix">Hello,<br>
In many programs that blind people come in contact with, k, or
ctrl+k, set bookmarks, so having k makes perfect sense.<br>
<br>
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?<br>
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.<br>
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.<br>
But this is almost getting into something Reaper should do and
not an accessibility plugin.<br>
Thanks,<br>
<br>
<div class="moz-signature"> <a moz-do-not-send="true"
href="http://www.brandonkeithbiggs.com/">Brandon Keith Biggs</a></div>
On 2/23/2015 7:11 PM, Derek Lane via RWP wrote:<br>
</div>
<blockquote cite="mid:B72F4D2C6ED742B187217539B1F6EA34@Ruby"
type="cite">This eliminates the logical key to asign a marker. <br>
ok, m? we'll go with the second letter, a? oh wait, that's to
arm a track. <br>
No problem, r then? oh wait, no. That's record, k perhaps? <br>
Sure, k to put down a time marker. <br>
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. <br>
<br>
<br>
<br>
<br>
<br>
----- Original Message ----- From: "Scott Chesworth via RWP" <a
moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="mailto:rwp@bluegrasspals.com"><rwp@bluegrasspals.com></a>
<br>
To: "Reapers Without Peepers" <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:rwp@bluegrasspals.com"><rwp@bluegrasspals.com></a>
<br>
Sent: Monday, February 23, 2015 4:59 AM <br>
Subject: Re: [Rwp] OSARA key map <br>
<br>
<br>
<blockquote type="cite">Hi Brandon, <br>
<br>
I'm curious about something. Taking mute as an example, why
would you <br>
want M and Shift+M to mute and unmute, when just M could act
as a <br>
toggle, so one press mutes, the next press unmutes. My
thinking is <br>
that if it's a toggle, it then frees up Shift+M to be used for
<br>
something related to muting that applies to a wider range of
tracks, <br>
but what's yours? <br>
<br>
Cheers <br>
<br>
Scott <br>
<br>
<br>
On 2/23/15, Brandon Keith Biggs via RWP <a
moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="mailto:rwp@bluegrasspals.com"><rwp@bluegrasspals.com></a>
wrote: <br>
<blockquote type="cite">Hello, <br>
I agree, build the keymap for the newbies and not for the
power users. <br>
a and shift+a for arm and un arm, s + shift s for solo and
unsolo, m + <br>
shift s for mute and un mute and the right and left arrow
keys for <br>
moving forward and back in the key map. <br>
Thanks, <br>
<br>
Brandon Keith Biggs <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="http://www.brandonkeithbiggs.com/"><http://www.brandonkeithbiggs.com/></a>
<br>
On 2/23/2015 3:28 AM, Scott Chesworth via RWP wrote: <br>
<blockquote type="cite">Hey Jamie, <br>
<br>
Wouldn't worry about overwriting the default bindings.
because it's <br>
widely acknowledged that they suck anyway. There are tons
of forum <br>
threads about it. It seems like one of the first things
sighted Reaper <br>
users do once they start trying to improve upon their
productivity is <br>
build their own keymap. I haven't yet heard of a case
where such a <br>
sighted power user transitions over to using Reaper with a
screen <br>
reader and starts screaming blue murder about their keymap
being <br>
munched. <br>
<br>
Personally, I'd vote we hash out a keymap on here however
the heck <br>
that could be done productively and work toward that
automated <br>
install. That way, if anybody has a little more work to
do, it's the <br>
power users instead of the people picking Reaper up for
the first <br>
time. Smoother entry for the newbies, and less support. <br>
<br>
Scott <br>
<br>
On 2/22/15, James Teh via RWP <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:rwp@bluegrasspals.com"><rwp@bluegrasspals.com></a>
wrote: <br>
<blockquote type="cite">On 23/02/2015 8:19 AM,
adriandavids404--- via RWP wrote: <br>
<blockquote type="cite">I stand to be corrected, but I
do think Reaaccess does allow the user <br>
to <br>
choose if the Reaaccess key map should override the
user's key map? <br>
</blockquote>
My apologies for being unclear. You're correct; it does.
What I meant is <br>
that (assuming I'm not incorrect) you have two options:
override the <br>
keymap *completely* or don't install it at all. That is,
if you've made <br>
changes before installing it, you can't keep those
changes while also <br>
installing the ReaAccess keymap. <br>
<br>
Jamie <br>
<br>
-- <br>
James Teh <br>
Email/MSN Messenger/Jabber: <a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:jamie@jantrid.net">jamie@jantrid.net</a>
<br>
Web site: <a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="http://www.jantrid.net/">http://www.jantrid.net/</a>
<br>
Twitter: jcsteh <br>
<br>
_______________________________________________ <br>
RWP mailing list <br>
<a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:RWP@bluegrasspals.com">RWP@bluegrasspals.com</a>
<br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://bluegrasspals.com/mailman/listinfo/rwp">http://bluegrasspals.com/mailman/listinfo/rwp</a>
<br>
<br>
</blockquote>
_______________________________________________ <br>
RWP mailing list <br>
<a moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:RWP@bluegrasspals.com">RWP@bluegrasspals.com</a>
<br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://bluegrasspals.com/mailman/listinfo/rwp">http://bluegrasspals.com/mailman/listinfo/rwp</a>
<br>
</blockquote>
<br>
<br>
</blockquote>
_______________________________________________ <br>
RWP mailing list <br>
<a moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:RWP@bluegrasspals.com">RWP@bluegrasspals.com</a>
<br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://bluegrasspals.com/mailman/listinfo/rwp">http://bluegrasspals.com/mailman/listinfo/rwp</a>
<br>
<br>
</blockquote>
<br>
_______________________________________________ <br>
RWP mailing list <br>
<a moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:RWP@bluegrasspals.com">RWP@bluegrasspals.com</a>
<br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://bluegrasspals.com/mailman/listinfo/rwp">http://bluegrasspals.com/mailman/listinfo/rwp</a>
<br>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
RWP mailing list
<a class="moz-txt-link-abbreviated" href="mailto:RWP@bluegrasspals.com">RWP@bluegrasspals.com</a>
<a class="moz-txt-link-freetext" href="http://bluegrasspals.com/mailman/listinfo/rwp">http://bluegrasspals.com/mailman/listinfo/rwp</a>
</pre>
</blockquote>
<br>
</body>
</html>