FR: "SWS: Select previous folder" and "SWS: Select next folder" to be a little smarter #981
Comments
Hi, modifying existing actions is always a little problematic imo because of the risk of breaking existing workflows. So I've added two new actions for the next SWS version called "SWS: Select nearest previous folder" and "SWS: Select nearest next folder" which behave the way you're suggesting. |
nofishonfriday
added a commit
to nofishonfriday/sws
that referenced
this issue
May 15, 2018
…WS: Select nearest next folder" (reaper-oss#981)
Thanks for the super speedy response! Point taken re modifying
existing actions, and many many thanks for adding the two new ones.
Looking forward to taking them for a spin whenever the next release
drops. :)
…On 5/15/18, nofish ***@***.***> wrote:
Hi,
modifying existing actions is always a little problematic imo because of the
risk of breaking existing workflows.
So I've added two new actions for the next SWS version called "SWS: Select
nearest previous folder" and "SWS: Select nearest next folder" which behave
the way you're suggesting.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#981 (comment)
|
Test build (Win x64): |
Thanks dude. From my initial tests, these behave exactly as I was
hoping! I'll post back if the other testers discover anything weird.
…On 6/16/18, nofish ***@***.***> wrote:
Test build (Win x64):
https://www.dropbox.com/s/vdwek7ynpv8wx66/reaper_sws64.dll?dl=1
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#981 (comment)
|
nofishonfriday
added a commit
to nofishonfriday/sws
that referenced
this issue
Jan 21, 2019
…oss#981)' - revert changes in whatsnew.txt (for avoiding merge conflict)
X-Raym
added a commit
to X-Raym/sws
that referenced
this issue
Jan 21, 2019
…arest_next_folder__(reaper-oss#981)' of https://github.com/nofishonfriday/sws into 2019-01
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
Currently, these two actions only work when a folder track is selected. Would it be possible to modify them so that if a user is on a standard track when they trigger the actions, they land on the nearest folder in either direction?
Example: let's say I have 12 drum tracks contained within a folder called "Drum bus", followed by two bass tracks which aren't folders, and below those, let's say 6 guitar tracks contained within a folder called "Guitar bus".
Currently, to navigate between those two folders using the SWS actions, I have to have one of the existing folders selected first. IE, if my snare track is selected, it's not possible to hit the keystroke I've bound to "SWS: Select next folder" and move to the "Guitar bus" folder.
This change would make folder navigation way more intuitive, and be massively appreciated by a whole bunch of blind users that I'm involved in putting a keymap together for.
Thanks for considering,
Scott
The text was updated successfully, but these errors were encountered: