[Solved] Best way to enable/disable mousehwheel action via toolbar

[MixR]

I have the action Script: Move contents of items left right by grid unit (mousewheel).lua set to alt+mousewheel but keep accidentally using it. Therefore I would like to toggle it via a toolbar icon/action.
When I create a toolbar action, however, it runs the command as opposed to enabling/disabling it. Seeing there is no universal toggle enable/disable following action command I am scratching my head.

[AB1]

https://forum.cockos.com/showthread.php?t=245955

Have not tested this with a mousewheel triggered action. Let us know if it works.

[AB1]

Was able to test this today. Yes, it works.

[MixR]

Originally Posted by AB1

Was able to test this today. Yes, it works.

Thank you so much for your reply and suggestion.
Having tried to follow the instructions in the post you linked to I am failing at getting this to work. My cycle action is:

IF
_S&M_DUMMY_TGL1
_RS5e9f46d126ea0ab3066f4d00aac191f9f6d85112 (Script: Move contents of items left right by grid unit (mousewheel).lua)
 ENDIF

With the action above assigned to the shortcut alt+Mousewheel
nothing happens - the assigned action is never triggered regardless of the toolbar action's state.

[AB1]

You're welcome.

You have probably already done this but just check that your toolbar button is set to the same dummy toggle as in the cycle action and that the toolbar button highlight toggles on and off to confirm that it is working. You should also see the 'state' column in the action list showing the on or off state, though this does not update in real time so you will need to close and re-open the action list window or something like that to get the state to update.

Your cycle action looks good although in my cycle action editor I do not see the script description directly following the command ID (it is in the next column) although that may just be how you have copied and pasted into this forum post. There should also not be a space before the ENDIF. Make sure you added these items to the cycle action by right clicking and choosing the appropriate option rather than just typing them in. I'm sure you did it right but just in case. Also check you 'apply' the action and that your chosen keyboard shortcut is then set to the cycle action rather than the action or script you actually want to trigger.

The other thing you could try is setting up another cycle action using dummy toggle 2 and a native REAPER action rather than a script, with a simple keyboard shortcut rather than one that uses the mousewheel. The mousewheel DOES work but just to keep things simple to get it working.

[MixR]

Originally Posted by AB1

You're welcome.

You have probably already done this but just check that your toolbar button is set to the same dummy toggle as in the cycle action and that the toolbar button highlight toggles on and off to confirm that it is working. You should also see the 'state' column in the action list showing the on or off state, though this does not update in real time so you will need to close and re-open the action list window or something like that to get the state to update.

Your cycle action looks good although in my cycle action editor I do not see the script description directly following the command ID (it is in the next column) although that may just be how you have copied and pasted into this forum post. There should also not be a space before the ENDIF. Make sure you added these items to the cycle action by right clicking and choosing the appropriate option rather than just typing them in. I'm sure you did it right but just in case. Also check you 'apply' the action and that your chosen keyboard shortcut is then set to the cycle action rather than the action or script you actually want to trigger.

The other thing you could try is setting up another cycle action using dummy toggle 2 and a native REAPER action rather than a script, with a simple keyboard shortcut rather than one that uses the mousewheel. The mousewheel DOES work but just to keep things simple to get it working.

Thank you for the great troubleshooting instructions. I have checked all the above (and yes, I pasted the action text in for readability) but am still getting nothing.
However, a second dummy action/toolbar button with a keyboard shortcut does work so it looks that I have done everything correctly in principle

[AB1]

Hmmm. That's odd. It may be possible that particular script is bypassing the normal shortcut system and doing its own keypress and/or mousewheel detection. That might explain it. I don't have access to ReaPack on this computer so cannot have a look at it right now but will get to it later today.

[AB1]

Looks like the script you are using is not in ReaPack but I found the thread where it likely came from.

If this is it...
https://forum.cockos.com/showthread.php?t=245914
...then I was right about the problem.

The 'reaper.get_action_context()' function is getting the mousewheel up or down state directly, as the script is triggered. But using a cycle action 'in between' the shortcut and the script means the script is not triggered DIRECTLY by the mousewheel so there is no 'action context' for the mousewheel and the script does not run as expected.

OK. Plan B. Keep the dummy toggle on your toolbar but ditch the cycle action. I use scripts for even the simplest custom actions and this is a good example of why.

Try this as your Alt+Mousewheel script. Don't forget to paste in YOUR commandID's for the other 2 scripts within this one.

togState = reaper.GetToggleCommandState(reaper.NamedCommandLookup("_S&M_DUMMY_TGL1"))
if togState == 1 then
  newValue,_ ,_ ,_,_,_ , val = reaper.get_action_context()
  if newValue then
      if val > 0 then
        reaper.Main_OnCommand(reaper.NamedCommandLookup("_RS61d51f1869daa4307621c3969136eb2b1ff20713"), 0) -- Script: me2beats_Move item content left one grid unit.lua
      else
        reaper.Main_OnCommand(reaper.NamedCommandLookup("_RSd2eaaeb59f562f0366fcf689fe210d070cc207b7"), 0) -- Script: me2beats_Move item content right one grid unit.lua
      end
  end
end

[MixR]

Originally Posted by AB1

Looks like the script you are using is not in ReaPack but I found the thread where it likely came from.

If this is it...
https://forum.cockos.com/showthread.php?t=245914
...then I was right about the problem.

The 'reaper.get_action_context()' function is getting the mousewheel up or down state directly, as the script is triggered. But using a cycle action 'in between' the shortcut and the script means the script is not triggered DIRECTLY by the mousewheel so there is no 'action context' for the mousewheel and the script does not run as expected.

OK. Plan B. Keep the dummy toggle on your toolbar but ditch the cycle action. I use scripts for even the simplest custom actions and this is a good example of why.

Try this as your Alt+Mousewheel script. Don't forget to paste in YOUR commandID's for the other 2 scripts within this one.

togState = reaper.GetToggleCommandState(reaper.NamedCommandLookup("_S&M_DUMMY_TGL1"))
if togState == 1 then
  newValue,_ ,_ ,_,_,_ , val = reaper.get_action_context()
  if newValue then
      if val > 0 then
        reaper.Main_OnCommand(reaper.NamedCommandLookup("_RS61d51f1869daa4307621c3969136eb2b1ff20713"), 0) -- Script: me2beats_Move item content left one grid unit.lua
      else
        reaper.Main_OnCommand(reaper.NamedCommandLookup("_RSd2eaaeb59f562f0366fcf689fe210d070cc207b7"), 0) -- Script: me2beats_Move item content right one grid unit.lua
      end
  end
end

Thank you!
That worked very nicely. Unfortunately even this basic level of coding is too difficult for me - though I do understand what each step is supposed to be doing. But how on earth I would ever be able to do this myself I have no idea

[AB1]

Glad you got this working.

I will make a note in the first thread I linked to, of the problem with running some scripts from within a custom or cycle action. I should have realised that. I am aware this is the newbieland sub-forum and that is why I initially recommend a cycle action rather than a script, even though scripts are more versatile. The explanation part above was included to help anyone else reading this.

Originally Posted by MixR

But how on earth I would ever be able to do this myself I have no idea

I am not going so say that "everyone should learn to code" but I will say this. It looks much more complicated than it is and the fact that you understand what each step is supposed to be doing is far more important for a beginner than knowing exactly what 'newValue,_ ,_ ,_,_,_ , val = reaper.get_action_context()' means.

Hopefully you can see that the first two and last lines in the script above are doing the same thing as the cycle action was trying to do, and that you could use those lines in a new script with any other action or script (indented with a single 'tab' as above) that you wished to be able to disable. The same dummy toggle number can optionally be used so that you can enable/disable a group of actions or scripts with a single toggle button if required.