[RWP] Off By One

[Jim Snowbarger]

Final chapter, in my desperate, and perhaps vain  quest for sanity. 
Updating to the latest reaper fixed the off by one track index problem.  So, 
that's good.
But, jaws users will want to know that, somewhere along the way, the 
standard jaws scripts got broken.   So, most of the keys still speak, even 
if you turn the screen reader off, and control+space does not stop at the 
current position any more.  Who knows what other impacts this has.  I 
understand what is wrong, and will fix it sometime in the next 2 or 3 days, 
and make that available.
Near as I can tell, It's not a major deal.


----- Original Message ----- 
From: "Jim Snowbarger" <Snowman at SnowmanRadio.com>
To: "Reapers Without Peepers" <rwp at reaaccess.com>
Sent: Thursday, October 23, 2014 9:14 PM
Subject: Re: [RWP] Off By One


> Well, for what it's worth, it turns out that, when I enabled the automatic 
> arming, that is when the problem begins, and then persists, even if you 
> turn that off again.
> So, apparently, it is a bug surrounding automatic arming.
> Too bad,  I really wanted to use that.  So, it's off to a later version to 
> see what.
>
> ----- Original Message ----- 
> From: "Patrick Perdue" <patrick at pdaudio.net>
> To: "Reapers Without Peepers" <rwp at reaaccess.com>
> Sent: Thursday, October 23, 2014 12:31 AM
> Subject: Re: [RWP] Off By One
>
>
>> Sounds like track grouping got turned on at some point.
>> Check the track menu for "track grouping enabled." If it's on, turn it 
>> off, and see if that fixes things.
>>
>> On 10/22/2014 11:07 PM, Jim Snowbarger wrote:
>>> Guys,
>>> I'm just trying to set up a nice track template. Nothing fancy.  At some
>>> point in the setup, I get to the stage where reaper context menus seem
>>> to be off by one track.  If I arrow to track 2, the context menus are
>>> showing me input and output parameters for track 1.  And, if I change
>>> those, it affects track 1, not 2.  If I up arrow to track 1, the context
>>> key gets me the track menu, not the output stuff.  It doesn't start out
>>> that way, but it gets that way as a result of editing the settings.
>>> Is there something I might have done to cause that?  Or is it just being
>>> a bad boy once again.
>>> I'm running version 3.76 just to not deal with the context menu hassle,
>>> and since there isn't really anything I need in the later versions.
>>> Unless it be absence of this lovely feature.  That would be nice. Can I
>>> prevent this?
>>> Or, Should I just scrap 3.76, and move on to the latest batch of bugs.
>>> Somewhere in the back of my mind is the nagging notion that, if they
>>> spent half as much time worrying about correct, reliable operation as
>>> they do over color tinting and icon saturation, we'd have a better, more
>>> usable  product.
>>>
>>>
>>> _______________________________________________
>>> 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
>