Hi,
yes, this is possible. This is done in the input assignment. You just have to create a new connectionSet. The open the keyboard entry in the left input tree and seach for the entry of the spacebar (important: There are 4 subfolders for "no additional key", "control" and "shift". Go into the correct folder to drag&drop the spacebar entry into the created connectionSet. Then rightclick on a free area in the connectionSet and select "Add"=>"Cuelists"=>"Cuelist". Then go into the Settings of the Cuelist Node and select your Cuelist. Then you can connect the Spacebar Node with the GO input of the Cuelist Node and you can step thru the cuelist with the spacebar.
JP
P.S.: It's totaly fine to ask those questions. Among others, we host our forum for this use case 
The question is, what do you mean, when you are talking about the "current active cuelist? Do you mean the currently running cuelist oder do you mean the cuelist currently in the cuelist editor? The first option would be no problem, because you can get the information, if a cuelist is running or not in the cuelist node in the Input Assignment. However, the second option can currently not be solved. The reason for that is, that there is currently no node in the Input Assignment, which reflects the Cuelist Editor so you can not control this window from within the Input Assignment. I stumbled over this lack of functionality a few weeks ago and was about to implement such a node in DMXControl 3.3.0. I needed a node to scroll in the Cuelist Editor because I wanted some kind of button to jump up and down in the editor. However, there are some ideas and issues in the concept of such a node, which I have to solve first. In addition, we have currently a feature freeze (to get the release of 3.3.0 done) so I can not include this new node anyway. But I'm planing to implement such a node in a future version of DMXControl 3
Ah yes, I mean the cuelist currently visible in the cuelist editor - exactly the same functionality as the Ctrl-G keyboard shortcut currently has.
An alternative solution would be to have user-customisable keyboard shortcuts like many other applications have. This could be achieved using a simple XML file, to avoid having to create a new user interface for editing keyboard shortcut assignments.
From a live show or theatre operation perspective, it's important to be able to easily press GO to move on to the next cue, while you're also reading the script or watching for a visual cue on stage.
The biggest, easiest button to press on a keyboard is the spacebar. Pressing the spacebar is much easier than pressing the two-key combination of Ctrl + G, or clicking the small green GO icon in the user interface using a mouse
From a live show or theatre operation perspective, it's important to be able to easily press GO to move on to the next cue, while you're also reading the script or watching for a visual cue on stage.
The biggest, easiest button to press on a keyboard is the spacebar. Pressing the spacebar is much easier than pressing the two-key combination of Ctrl + G, or clicking the small green GO icon in the user interface using a mouse
Yes, you are right. I usually have theater shows as well, so I see the issues, you have. Normally, I use my mouse, but to solve such issues in the short term, I sometimes use a MIDI control board with large buttons or my Stream Deck. With both I have an easy solution to work with it. However, I also have only one large cuelist with 100 - 200 cues as my main cuelist and therefore I can connect my external control board to this single cuelist.
An alternative solution would be to have user-customisable keyboard shortcuts like many other applications have. This could be achieved using a simple XML file, to avoid having to create a new user interface for editing keyboard shortcut assignments.
This is another and also bigger issue. We currently have no central keyboard management in DMXControl 3. Every control (cuelist editor, stage view,....) manages the shortcuts on its own. We know, that this is an issue and we have some ideas to solve it. However, those changes need some refactoring in many parts of DMXControl 3. So we can not address this issue yet.
My shows are usually a series of timecode-based cuelists, one for each song in the show, so I think my workaround will be to create a master cuelist with each song's cuelist being triggered from the master cuelist, and use input assignment to attach the spacebar to that master cuelist.
Thanks for the explanations
My shows are usually a series of timecode-based cuelists, one for each song in the show, so I think my workaround will be to create a master cuelist with each song's cuelist being triggered from the master cuelist, and use input assignment to attach the spacebar to that master cuelist.
This looks like a good solution for your setup
Thanks for the explanations
No problem
