Function Keys as "Modes"

Cool workflow idea! It can be done with globalstate This should get you started :

Here's the script that will go on your F keys, generate as many "Modes" as you want by duplicating this script and chaning the 'Mode #' For this example I've given you 2 modes but you can expand as much as you want

SET MODE 1 (Put this on your F1 or stream deck or wherever you want to switch modes)

globalState.modeChoice = 'Mode 1';

Here's the Button for SET Mode 2

globalState.modeChoice = 'Mode 2';

As you can see you can make any number more of scripts to increase your mode numbers by simply duplicating and changing the number in the text.

Then here's the script you would duplicate and populate to your numeric 1-9 which reads the globalstate.modeChoice and triggers the approriate
'behaviour'.

if (globalState.modeChoice === 'Mode 1'){
    log('Mode 1') /// Replace this log with the function (behavior) you want in MODE 1
}
if (globalState.modeChoice === 'Mode 2'){
    log ('mode 2') /// Replace this log with the function (behavior) you want in MODE 2
}
if (!globalState.modeChoice){
    log ('No Mode Yo') /// This one is here to tell you you have not enabled a globalstate yet.
}

As you can see you can add any more number of

if (globalState.modeChoice === 'Mode #'){
///Your code Goes here
}

As you'd like, to increase the number of modes along with the Globalstate mode Buttons.

The time consuming part is going to be building your 1-9 buttons each with all the correct funcitons in each slot.

Really cool workflow idea though, I may try and template this to work with commandID's for easy plug and play for people when I find myself with some free time.

Bests,
Owen

Thanks so much for getting me started guys...I'm still tip toeing into the scripting, quite good at editing existing ones, but nowhere near the point of creating them from scratch so this is a massive help!

I haven't explored creating custom surfaces yet, but presumably this would also be easy enough to create a small overlay window that could sit in the blank space to the right of the transport, showing the mode name that I'm currently in? Colour coded for each one etc.

This could be homework for the next few days!

Edit.... I got that working pretty fast thanks to your help. A followup question;

Is it possible to define these globalState via different kinds of actions other than keystrokes? Such as clicking a certain part of the UI, or a certain condition like a particular plugin window is open? Or a clip being selected in the arrange page? I presume it's possible and these will all have very different codings to define them, so any pointers on where to find a summary of these would be useful.

I need to dig into the surface readout for the mode I'm in, but I presume that is possible?

Finally is it possible to have keystrokes behave as an on off toggle? So hitting F1 puts it into mode 1, but hitting F1 again takes it out of Mode 1 and back into No Mode Defined? This could be useful for this but also for showing and hiding the onscreen Decks just on one key

Thanks again