James Teh

So, getting back to my question, would changing this to f2 make it any better? Is this one of the "usual tricks" most people would try? Justin?

Technically, I could change this to enter. The problem I have with that is that in a dialog, enter has always meant "press the default button"; e.g. the OK button....

Sorry; hit submit prematurely. Note that Even a sighted user can't see what is copied; they make that determination entirely based on what's selected. Can you elaborate regarding the issues...

Overall, I think this is a good idea. There are two points worth noting, though: 1. This could be a huge amount of info because there are many kinds of...

A message box with HTML is a great idea, but it's not something I can do without a huge amount of additional work. It'd also have to be done entirely...

I had the same thought, but standard edit fields don't support paragraph navigation, unfortunately. I could try to hack this in, but I'm not sure how feasible it is yet.

I think deciding to skip certain information is a very slippery slope. You want this command precisely to give the user as much info as possible, reflecting what sighted users...

That's fair, though there's significant implementation cost in adding things like this. I guess it's a matter of making a call as to whether we should just not implement this...

Another UX complication. When we're reporting selection for just items, we report all the selected items, prefixing each with its track number; e.g. 1.1, 2.1, etc. My original idea for...

It is a bit tricky, but the main concern is that it's inconsistent with the rest of REAPER. For example, the builtin commands to select tracks, items and envelope points...