[Rwp] OSARA keymap

[Scott Chesworth]

Jamie wrote:
1. I don't think it makes sense to report actions that aren't obvious
to sighted users either. That is, it makes sense for a screen reader
user to have the same experience.

SC: In this example, and any others that I can think of come to that,
there is some visual indication from changes in the wave forms on
screen though. Even if that's not the case, many people have that last
undo point at the end of the menu bar and could glance up to see
whether that'd changed.

Jamie wrote:
2. Where actions *are* obvious to sighted users (which I'll grant is
most of them), just echoing the action is flawed because you don't
know that it really happened. Using your example, if there are no
selected items, it would be potentially confusing to say "Stretch and
fit items to time selection" because it didn't actually succeed.

SC: I find Reaper tends to be fairly good at complaining when it's not
been able to do what you told it to. For example, if I hit Shift+S to
split based on a time selection without a time selection being
specified, it can't complete the action and tells me so. Same deal if
I try to view plugin parameters on a track but no track is selected,
or there are plenty of other examples if they'd be helpful. Would it
be worth examining those actions to see whether their way of shouting
at you when stuffs gone wrong could be reused?

Scott

On 2/24/15, James Teh via RWP <rwp at bluegrasspals.com> wrote:
> On 24/02/2015 3:58 AM, Derek Lane via RWP wrote:
>> As far as the tab and shift+tab transient navigation goes, playback
>> doesn't follow the cursor, but the actions we chained together makes
>> this the case.
>> The automatic playback of items is another excellent means of seeking
>> through a large project.
> I agree this probably makes sense while playing. So, ideally, you want
> it to move the edit cursor like it does now, but also move the play
> cursor while playing? And you want this for both transients and items?
> The question is whether I should add a "Move play cursor to edit cursor"
> action which you can chain or just tweak the in-built actions. Normally,
> I'm not a fan of tweaking in-built actions, but I make an exception for
> cases like this where the behaviour is more intuitive anyway. Thoughts?
>
>> It would be nice to have an action which would echo the previous action.
>> For example, reaaccess speaks when you do things like stretch and fit
>> items to time selection, add tempo changes, etc.  Rathe than attempt
>> to make everything speek, adding an "echo last action" function would
>> give keymap designers the ability to speek or not speek sertain actions.
> I have two main problems with this:
> 1. I don't think it makes sense to report actions that aren't obvious to
> sighted users either. That is, it makes sense for a screen reader user
> to have the same experience.
> 2. Where actions *are* obvious to sighted users (which I'll grant is
> most of them), just echoing the action is flawed because you don't know
> that it really happened. Using your example, if there are no selected
> items, it would be potentially confusing to say "Stretch and fit items
> to time selection" because it didn't actually succeed.
>
> 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
>