[RWP] Applications key no longer triggers context menu

[Indigo]

Let's be polite with each other, okay?
I add and remove sends and receives from the IO dialog, brought up with 
the letter I, so never missed those menus.
If you are on a selected track, its send and receives will show up in 
the IO dialog.


On 1/8/2014 7:23 PM, Drew wrote:
> That's how you add and remove sends. I believe we've told you this about
> a million times (rounded down.) It's rather annoying as it's just about
> the only thing that broke between Reaper 3 and Reaper 4, that I can
> tell. You can work around it by using the routing matrix of course (I)
> but it's usually a more efficient workflow to be able to check and
> uncheck them in the menu, rather than the somewhat cumbersome task of
> tabbing around the dialog to remove them and remembering the 1-second
> rule when adding them.
> ----- Original Message ----- From: "Indigo" <33indigo at charter.net>
> To: "Reapers Without Peepers" <rwp at reaaccess.com>
> Sent: Wednesday, January 08, 2014 2:34 PM
> Subject: Re: [RWP] Applications key no longer triggers context menu
>
>
>> Please tell me what the other menus with shift/control are for, and
>> what screen they begin with?
>> Like the recording options menu displays Monitor Input when you arrow
>> down once.
>> I sometimes get other menus from the applications key, like one that
>> says J Jump to marker something.
>>
>> I know for sure there's a setting that could be a permanent fix,
>> because once I spent hours and accidentally ran across it, but later
>> couldn't discover what setting did it.
>> I'd also like to know why sometimes I get the standard file, edit,
>> view, etcetera menus when I press alt, and sometimes not.
>> With that too, usually when I bring up those menus with a press of
>> F10, then alt continues to bring them up during that session, though
>> not 100 percent consistently.
>> Those are just slightly annoying bugs, and not show stoppers for me,
>> as long as we can discover workArounds.
>> David Shortland's discovery of a second midi editor that's much more
>> complete than the original midi editor; when something broke the
>> original editor's ReaAccess shortcut; turned out to be a blessing in
>> disguise.
>> Thanks,
>> Indi
>>
>> On 1/8/2014 4:54 PM, T.Reid wrote:
>>> Thanks Indy. I tried this workaround, but it only seems to present the
>>> context menu available from the applications key alone. Meaning the
>>> different menus with shift, control... are no longer available. Do
>>> you get
>>> these in 4.x?
>>>
>>> I wonder if figuring out what went wrong or changed could be helpful in
>>> getting the applications key back in 4.xxx? When I do a Ctrl Insert
>>> F2 in
>>> Jaws it confirms that the child window handle is invalid along with
>>> others.
>>>
>>> t
>>>
>>> -----Original Message-----
>>> From: RWP [mailto:rwp-bounces at reaaccess.com] On Behalf Of Indigo
>>> Sent: Wednesday, January 08, 2014 4:41 PM
>>> To: Reapers Without Peepers
>>> Subject: Re: [RWP] Applications key no longer triggers context menu
>>>
>>> Looks like your 3.7 version has whatever causes the Handle not found
>>> issue
>>> in Reaper 4x.
>>> I fooled around with various settings in Reaper and got the recording
>>> options context menu to display, and then not to display, in Reaper 4x
>>> versions.
>>> You can always try the fix used by 4x users, hold ctrl then up arrow a
>>> couple of times.
>>> Then the problem is gone, so that a press of the applications key
>>> displays
>>> the menu for that session.
>>> It's not a permanent fix in versions 4x, you need to do ctrl+up arrow
>>> again
>>> next session.
>>>
>>>
>>> On 1/8/2014 12:41 PM, T.Reid wrote:
>>>> Hello All:
>>>>
>>>> I'm hoping someone can help. I am running Reaper 3.76 with Reaaccess
>>>> and have been for quite some time now.
>>>>
>>>> I am not aware of any changes that I made, but when in the Track View
>>>> and positioned on a track when I press the Applications key instead of
>>>> getting the context menu, Jaws announces "Handle of current track
>>>> who is
>>> not found"
>>>>
>>>> I have no clue what that means, but it seems like it may be some sort
>>>> of configuration issue because I reinstalled Reaaccess and still get
>>>> the message. As far as I know I haven't changed anything on this
>>>> machine. It was working fine  on Monday when in Reaper.
>>>>
>>>> Any suggestions are welcomed!
>>>>
>>>> Thanks,
>>>> t
>>>>
>>>>
>>>> _______________________________________________
>>>> RWP mailing list
>>>> RWP at reaaccess.com
>>>> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com
>>>>
>>>
>>> _______________________________________________
>>> RWP mailing list
>>> RWP at reaaccess.com
>>> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com
>>>
>>>
>>> _______________________________________________
>>> RWP mailing list
>>> RWP at reaaccess.com
>>> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com
>>>
>>
>> _______________________________________________
>> RWP mailing list
>> RWP at reaaccess.com
>> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com
>>
>
>
> _______________________________________________
> RWP mailing list
> RWP at reaaccess.com
> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com