[QLab] Stop all cues but one?

[Calliope Georgousi]

Hi there guys,

I found a script to make all cues stop, which works nice for me but what I want to do is to kill/stop all cues but ( a specific) one (or two maybe! :-).

Any ideas on how to achieve this please?

Best,
Calliope Georgousi
BSc Multimedia Technology & Design
Brunel University, Uxbridge

Room 2
Block E
Flat 46
Isambard Complex
UB8 3FG
UK
www.calliopemuse.co.uk
Mob tel: +44 7564 042023
skype name: calliope8

[Charlie Richmond]

On Wed, 17 Mar 2010, Calliope Georgousi wrote:

> I found a script to make all cues stop, which works nice for me but what I want to do is to kill/stop all cues but ( a specific) one (or two maybe! :-).
>
> Any ideas on how to achieve this please?

Send an MSC STOP Cue command, specifying the cues you want to stop.

C-)

________________________________________________________
WHEN REPLYING, PLEASE QUOTE ONLY WHAT YOU NEED. Thanks!
Change your preferences or unsubscribe here:
http://lists.figure53.com/listinfo.cgi/qlab-figure53.com

[Rich Walsh]

On 17 Mar 2010, at 02:32, Calliope Georgousi wrote:

> I found a script to make all cues stop, which works nice for me but
> what I want to do is to kill/stop all cues but ( a specific) one (or
> two maybe! :-).

Something like this:

set dontStopMeNow to {"3", "4"} -- Define list of cue numbers not to
stop (NB: they must be strings)

tell front workspace
repeat with eachCue in (active cues as list)
if q number of eachCue is not in dontStopMeNow then
if q type of eachCue is "Group" then
if mode of eachCue is not cue_list then
stop eachCue
end if
else
stop eachCue
end if
end if
end repeat
end tell

This uses Chris's new scripting hook from 2.2.7 onwards ("active
cues") - although this variable does return cue lists as well as cues,
so you have to put some ifs in there to prevent the script stopping
the whole cue list (I'm sure there's a more elegant way of
constructing that bit, but I can't find it this morning).

Rich

[Christopher Ashworth]

On Mar 17, 2010, at 4:22 AM, Rich Walsh wrote:
>
> This uses Chris's new scripting hook from 2.2.7 onwards ("active
> cues") - although this variable does return cue lists as well as cues,

Ah--whoops--that list was intended to match what appears in the Active
Cues panel.

[...goes to check code...]

Ah yes, it looks like I set the scripting dictionary to get the
unfiltered list, rather than the filtered list.

Thanks for the catch Rich!

-C