In my global rackspace I have a widget for moving from song part to song part.
I operate it from a foot pedal, alternatively from a button on my keyboard.
Sometimes it feels too easy to make a double click, moving two songparts forward, which can be quite the crisis when playing live 
Is there a way to avoid that? Some kind of scripting not allowing two clicks to be sent?
Why don’t you lock a widget?
It will be locked for GUI operations in the Panels view, but it will respond to MIDI if mapped to a controller.
That’s not my problem. I don’t qlick the widget, I click the keyboard button or foot pedal.
Far too often, if I do not check my setlist view visually, my clicking operation has had me jumping over one song part
I pieced together a rough script that moves to the next song when a widget with a handle of Next is pressed. It adds a 500ms check for the press of the widget, and ignores any additional presses that happen within that 500ms time.
Perhaps you can adapt it for your use.
Var
Next : Widget
Done : Boolean
Start : Ramp
On WidgetValueChanged(newValue : double) from Next
If Done == false then
If newValue > 0 then
Done = True
SetGeneratorLength(Start, 500)
EnableGenerator(Start, true)
SetTimersRunning(true)
NextSong()
End
End
End
On GeneratorEndCycle(x : integer) from Start
Done = false
End
Thx a lot!
That was the kind of solution I thought about. I’ll see if it can be adapted to work for song parts.
And thx for the edit of the title line! Was in a hurry and didn’t notice the error.
Should Next() instead of NextSong() do the job, walking through the setlist songpart after songpart?
SongNextPart() should work. You could try Next() also and see what happens!
Thx! Didn’t imediately find it in the function documentation, but found it now
Will do some testing tomorrow.