[Rwp] Reporting item selection with OSARA [was: Fading out]

Scott Chesworth scottchesworth at gmail.com
Tue Oct 27 20:57:39 EDT 2015


I'm pretty sure you're right about the GitHub issue lol.

Personally, I'd rather hear something like added to selection. It
tells me what just happened, and assuming we're getting a separate
keystroke to query what's selected overall, it keeps the repeated info
to a minimum.

Scott

On 10/28/15, James Teh via RWP <rwp at bluegrasspals.com> wrote:
> Sounds fair to me. I actually didn't take into account that OSARA
> currently doesn't even report the item you've just selected. Sorry;
> brain fail. :)
>
> One minor question is whether "added to selection" is what we want or
> just the number of items now selected.
>
> I think there's even actually already a GitHub issue open for this.
>
> Jamie
>
> On 28/10/2015 10:49 AM, Scott Chesworth via RWP wrote:
>> Hi Jamie,
>>
>> In an ideal world, this is the ux I'd like for multiple item selection.
>>
>> When selecting with - let's say CTRL+Shift+arrows, I'd like action
>> feedback of each item name as I move onto it. In ReaAccess, these
>> announcements were preceded by the item number. For me, that item
>> number is superfluous more often than not, but I can imagine it being
>> useful for anyone who's dealing with thousands of short items where
>> naming them all wouldn't be a good use of their Reaping time. So, we'd
>> hit CTRL+Shift+Right and hear something like "4 2nd verse added to
>> selection". That way, the newbies have confirmation of what happened
>> if they care to wait long enough to hear "added to selection", and the
>> more confident users will hear the name of the item they've added and
>> can skip to the next. I'd like to be able to request info on what's
>> selected with a separate keystroke. When it comes to this, I found the
>> ReaAccess approach of only reporting a total number of items annoying,
>> because it's not always useful. Assuming some time went into making
>> that selection (grabbing items from multiple tracks for example),
>> hearing their names read out would be more informative and much more
>> useful for my workflows. The important thing is that we only hear that
>> potentially long list of info upon request, so the time spent
>> listening to it is a choice, hence my suggestion of a separate
>> keystroke to query it. If you could make that keystroke context
>> sensitive, so it'd tell me which tracks were selected if I'd selected
>> those, which items were selected if I'd selected those, perhaps a
>> start and end time if I've made a time selection etc, I'd be one happy
>> Reaper-er.
>>
>> Thoughts?
>>
>> Scott
>>
>> On 10/28/15, James Teh via RWP <rwp at bluegrasspals.com> wrote:
>>> On 28/10/2015 9:28 AM, Chris Belle via RWP wrote:
>>>> my only head scratching thing with reaper lately is how to know how
>>>> many items and which items you have selected.
>>>> When gluing and such and using the shift with the control and right
>>>> and left arrows like we did with reaccess doesn't give the same
>>>> feedback.
>>> Yup, reporting item selection is on my to-do list. One question, though:
>>> how would oyu want to be told which items are selected? As I understand
>>> it, when you select additional items, ReaAccess just tells you how many
>>> items are selected. Reporting every selected item every time you press
>>> ctrl+shift+rightArrow wouldn't be particularly eficient...
>>>
>>> Jamie
>>>
>>> --
>>> James Teh
>>> Executive Director, NV Access Limited
>>> Ph +61 7 3149 3306
>>> www.nvaccess.org
>>> Facebook: http://www.facebook.com/NVAccess
>>> Twitter: @NVAccess
>>> SIP: jamie at nvaccess.org
>>>
>>> _______________________________________________
>>> RWP mailing list
>>> RWP at bluegrasspals.com
>>> http://bluegrasspals.com/mailman/listinfo/rwp
>>>
>> _______________________________________________
>> RWP mailing list
>> RWP at bluegrasspals.com
>> http://bluegrasspals.com/mailman/listinfo/rwp
>
> --
> James Teh
> Executive Director, NV Access Limited
> Ph +61 7 3149 3306
> www.nvaccess.org
> Facebook: http://www.facebook.com/NVAccess
> Twitter: @NVAccess
> SIP: jamie at nvaccess.org
>
> _______________________________________________
> RWP mailing list
> RWP at bluegrasspals.com
> http://bluegrasspals.com/mailman/listinfo/rwp
>


More information about the RWP mailing list