Using these in my own templates

Thanks for posting a question or an issue related to the 'Multi-Function Buttons for Dummys' package.
This package is made by @Owen_Granich_Young. We're auto-tagging them here so that they will hopefully be able to help you.

Please note, that the best way to get help with a script, macro or other content installed from the Store is to select the script you installed, then click the red Need help button, and then click "Get help with this script or macro".
By using this workflow, the developer of the package will get access to more information so they'll be able to help you quicker.
You can read more about how to best get help in this article: bit.ly/sfscripthelp

Hey bud,

Yeah you deff actually want to work this into the code of your own template instead of using this one.

Here's the link to the original forum post where I learned how to build this template : Templating If/Or/Else what am I doing wrong?

Here's the slimmed down code for just no modifier and command that you'd work into your own template.

const modifierState = event.keyboardState.asString

switch (modifierState) {
    case "cmd":
        log("Command is held down");
        /// YOUR HOLD COMMAND CODE GOES HERE
        break
    case "":
        log("No Modifiers are held down");
        //// YOUR NO MODIFIER CODE GOES HERE
        break
};

Then you can template out from there, ideally with a single STRING Property for both the scroll to track or the create new track.

Sense making?

Owen

ps. When I'm not swamped I'm definitely going back to my ADR cuing Package and doing some updates from what we've been discussing.

pps. as the Original forum conversation mentions for anybody else seeing this. This will ONLY WORK on a Deck or surface. Not with keybindings.