Highlight and Session Box Navigation

1.27K viewsGeneralNavigation
0

Regardless of the physical controller any user is creating a script for… will the codes to move a highlight left/right or up/down be by-and-large the same? Same question for Session Boxes.

I know there’d be differences re the physical action of a single knob vs two buttons. But what I’m curious to know is, to get highlight nav to function as it should and navigate to the right of folded grouped tracks, would the underlying code required be the same regardless of controller?

If the code itself has to be different, are the steps required to set it up pretty much the same?

Update, 1 month since posting. 100+ views. No answers. So everyone elseĀ either thinks I’m a dumbass for not getting it, or they don’t use these functions.

I’m finding it an impenetrable process to learn how to set it up. I can build a multi-layered, cross-functional script for the nanoKontrol2, but I can’t for the life of me make highlight nav move right of a folded track group using the “>” button of the nK2’s Transport section (nor any other button). What’s frustrating, as a CSS license holder of 3 years now, is there’s never been a straight forward tutorial to just do THE most primary of functions. I thought it was going to be fixed with 2.8? Could we please have a dedicated blog post showing how to do this step-by-step. Thanks

James Henderson Answered question

Also… why does the default highlight navigation scroll tracks behaviour work with knobs, agnostic of whether folded group tracks exist, whilst button increment control stops at a folded group?

Scroll is using slightly different code to when incrementing/decrementing with buttons, which is likely why you’re experiencing these 2 different results.

I believe this bug has already been reported and logged for us to investigate.

Well hell. I typed a long reply, but pressed Esc because I got fed up with autocorrect changing Remotify to Remotely… which no longer happens now I pressed Esc once. See… Remotify. Huh. Well, in short…
– Not happy
– Implied “fixed in next major release” haven’t materialised
– Workaround using Reactions isn’t a fix, but it is still a workaround
– Other users recommending videos to watch so we can figure it out is not adequate support
– Please create a blog tutorial or series that details the Reactions workaround as a step-by-step How To
– Is this ‘step +/-1’ Reactions for highlight navigation ubiquitous enough for it to be added to On Remotify in CSS?
Thanks
Jus

0

Hi John, I curious why this bug is not yet fixed given it was reported so long ago. Can you shed some light, please?

Jushia Tuphou Answered question
You are viewing 1 out of 3 answers, click here to view all answers.