Renaming "Subcue"

[lttton]

What I found when training my colleagues with SCS is that there is always a mix-up with cues and subcues. The software should clearly show that each cue already contains a single subcue. The names could possibly be changed to "Trigger" and "Event" to clarify this. The appearance of the tree view in the editor could possibly be changed so that each cue / trigger contains a subcue / event.
Saludos

[Mike Daniell]

I think the term "Cue'" needs to stay, but I'm open to suggestions for an alternative term for "Sub-Cue".

[d_korman]

"Part" (as used by some lighting consoles )?

[lttton]

Yes Mike,
i can confirm.
A Cue is a Cue… but it contains one single trigger(activation method) and multiple events (subcues)
Regards

[Onno Rietveld]

I think that Cue must stay (Show CUE system...) but rename Sub-Cue sounds like a good idea. My suggestion is “Action”.

Regards, Onno

[am@umbc.edu]

I agree that when teaching the software "subcue" is a tough concept for students to understand. Also, Qlab uses "group cue" and "child" which I also think is problematic to explain and maybe puts an unneeded power structure in.
I like the idea of "part" as suggested above to mimic some lighting consoles.

[tocsin]

Whats wrong with Subcue? It is sub the first Cue. The name fits perfect. As soon a cue is triggered by a cue befor it is a Subcue. Or do i miss here something?

[lttton]

@tocsin
With your contribution you have provided proof that the naming is unfortunate. In fact, the first cue already contains a subcue. The cue sub this cue is then already the second subcue.This is confusing and has obviously confused you too.