[RWP] KeyMaps

[indigo]

I think this kind of discussion is  an excellent idea, Jim.
Actually, I've been trying to avoid Wineyes versus Reaper shortcut 
conflicts already, by either disabling or changing Wineyes shortcuts.
Now, I haven't used it for a while, but there's a Wineyes shortcut to 
hear the X Y screen coordinates, it's embarrasing that I can't remember 
it right this second, but anyway it conflicts with a default Reaper 
shortcut at the number pad.
Even before ReaAccess existed reaper made use of various  numpad key 
combinations, so when I'd try to hear screen coordinates I'd go to some 
unknown place in Reaper instead.
So, I just remapped Wineyes shortcut to a more intuitive one that was 
available in its own shortcuts
In that case,  thought it was easier to remap Wineyes than lose a 
possibly useful Reaper default shortcut, that I might need later.

I turned off Wineyes hot keys and cursor shortcuts, but I still run into 
a shortcut conflict somewhere around the F5 F6 keys, a Wineyes shortcut 
that usually defines user windows
So far, I haven't needed user windows, for Reaper,  which can restrict 
movement to a screen area of any size or shape; as small  as a single pixel.

I can handle such conflicts easily enough, but I find it fascinating 
that you've caught Reaper capturing key strokes that should be returning 
back to inform Jaws as to what is going on, is that what you said
It's probably capturing those same keystrokes before they can be used by 
Wineyes as well.
Can you tell me what application you are using to detect Reaper 
capturing key strokes?

I employ little workarounds every day, no big deal, like needing to push 
the middle insert key twice
When I have used ctrl+insert to bring up a VSTI synth, then want to 
bring in a midi file, I press the insert key by itself and it tries to 
take me again to the folders where plugs are stored, as if ctrl was 
still being held, instead of opening the insert media dialog.
Those kind of tiny glitches aren't worth fixing to me, as long as I can 
just press that insert key a second time to insert midi files into the 
project.
I think we should save fixes for the most serious malfunctions, maybe 
the media browser, which seems to me to need a total redesign, or maybe 
getting automation to work like folks expect it to.
Tim Burgess is in the midst of testing his second generation Mackie 
Display Reader on Reaper, and ProTools, as well as Sonar.
I'm not sure how much remapping goes on there, if any, but I know he 
wants feedback, so his MDR version 2 stays generic  for all daws, so we 
should keep Tim  informed.

I haven't made much use of my Behringer BCF2000 yet, only using the 
least exciting and useful mode, emulated mackie mode for sonar 3, which 
only seems to provide pans and control of audio tracks from the faders; 
but there are at least 2 full plans for the BCF2000 that I know 
extensively remap Reaper, Klinke's plug, plus fallofarcadia standard 
BCF2000 presetfor Reaper.
I somehow doubt that either of those could do ReaAccess much good, but, 
of course, we don't need to use those entire schemes when they harm 
ReaAccess.
Did you notice that when installing ReaAccess you have the choice of 
using ReaAccess map or default Reaper map, for advanced users only, or 
so the installer  says
I can't imagine what ReaAccess would be like without its cozy little 
custom qwerty working area.

With default Reaper mapping, what would remain of ReaAccess?

When I eventually learn all I need to know in Reaper, I would like to 
try 2 keyboards on it at once, maybe 1 for default ReaAccess mapping, 
and another for custom or default Reaper mapping.
I know that this computer I'm on right now can have a PS2 and a USB 
keyboard running simultaneously, I've done it with no apparent problems, 
don't know if that is true for all hardware, though.
So, count me in as an advocate for whatever works.
If JFW needs a workaround to reach something, or vice versa for Wineyes, 
I'd remat Wineyes to fit JFW moves when possible.
I eventually hope to know JFW, Wineyes and NVDA equally well, to ward 
off senility as long as possible. smile.

Unfortunately, if we remap to assist JFW or Wineyes, we might shut out 
NVDA or System Access, though.
I'm on N V D A right this second, and often wish I could remap its use 
of the middle insert key to something on my left, like the ` accent 
grave or tilda ~ key, though French and Spanish users might object to that.
When I'm in ReaAccess with N V D A I'm blocked from using ctrl+insert to 
bring in plugIns or the insert key alone to insert media.

Here's where someone who uses N V D A will tell me to use the caps lock 
key as an alternative NVDA key, okay, , but that doesn't release the 
middle insert key to ReaAccess; and when I use caps lock for the NVDA 
key, I get stuck typing all caps, so folks think I'm pissed off and 
yelling at them. smile.
So, what's the answer, can we really come up with  generic remapping?
We ought to at least be using the 8 or 10 shortcut combinations that 
aren't currently being used in ReaAccess.

Indigo L
On 4/2/2012 11:29 PM, Jim Snowbarger wrote:
> This message is not just a jaws discussion,  so read on for an interesting idea.
>
> I have been messing with the jaws scripting approach to improving how the media explorer works.  And, I've got something that seems to help anyway, and I'll be passing along a link to that in a few days.
> But, in working on that, I have discovered that there are lots of very strange irregularities regarding how key strokes are captured by reaper.  Usually, the control that will receive your key strokes is the control that has focus.  However, I have seen cases where this becomes not true.   situations  where reaper is capturing keystrokes before they get to jaws, so jaws never knows about them.  Very irregular stuff.
> But, the creation of hotkeys to quickly do things is, in general, a productivity enhancer, and an improvement in comfort.   And, if reaper has an action that will apply, it is definitely a preferred solution to use the reaper action.
>
> Anyway, it's apparent that reaper shortcuts are very important to us, and can be used to do some of the same things that  a jaws script might do.  But, it has the advantage of being significantly more stable in this particular environment, andalso of being screen reader independent.
> So, what if we started centrally accumulating a list of reaper action hotkey assignments that we all find useful, so we can all talk the same language about hot keys.
> ReAccess has already made lots of assignments.  But, this is a way in which we can extend ReAccess.
> These keymaps are just formatted text files.  It looks like an import operation grabs all the key assignments from one file, and uses them exclusively.  But, you should be able to open the reaper default keymap with a text editor, and insert additional key assignments, thereby effectively merging those new assignments into your current settings.
> Of course, gut wrenching, religious arguments break out whenever two or more people try to agree on an appropriate hot key choice.  So, that will make it hard.  But, if we could just figure out how to make the choice, and submit it to a growing common list, then we could all refer to the same key strokes when we talk about how to use such things, and the growing Wiki could reference them.
> Once, general consensus seems to accept a proposed assignment, we could add it to a central file that newbies could download.  And, those of us on the list at the time could store them locally.
> Anybody think this is a good idea?
>
> The discussion of a proposed addition would help make sure the action doesn't already exist somewhere, and help make reasonable hotkey choices.  Reaper and Reaccess is a land mine environment for hot keys.
>
> One pair of new actions I would like to assign is the ability to move directly to the start or end of a time selection.  I find this action is handy when confirming that the selection exists, and that it is set up the way I want it to be.
> I propose windows+leftArrow and windows+right arrow.
> I wanted to connected it to some form of bracet keys, since those are generally involved in selections.
> So, I would be ok with some choice like that too.
>
> BTW, I still find that, once I make a time selection with alt+shift+ left and right bracket, that, if I move to the start of the time selection, with my new hotkey, then press space, the selected portion is all I hear.
>
>
>
>
> _______________________________________________
> RWP mailing list
> RWP at reaaccess.com
> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com