[QLab] Modifying Cue Color Script

827 views
Skip to first unread message

Adam

unread,
Jul 23, 2011, 1:59:34 PM7/23/11
to ql...@lists.figure53.com
I've recently started using Stephen Swift's script for color coding
cues. However, I think it's missing one thing and I can't quite figure
it out. Is there a way to return the currently selected cue back to
it's color default?

Thanks,
Adam
________________________________________________________
WHEN REPLYING, PLEASE QUOTE ONLY WHAT YOU NEED. Thanks!
Change your preferences or unsubscribe here:
http://lists.figure53.com/listinfo.cgi/qlab-figure53.com
Follow Figure 53 on Twitter here: http://twitter.com/Figure53

Rich Walsh

unread,
Jul 23, 2011, 8:21:50 PM7/23/11
to Discussion and support for QLab users.
On 23 Jul 2011, at 18:59, Adam wrote:

> I've recently started using Stephen Swift's script for color coding
> cues. However, I think it's missing one thing and I can't quite figure
> it out. Is there a way to return the currently selected cue back to
> it's color default?

Assuming you mean this script, http://groups.google.com/group/qlab/browse_thread/thread/bf0eaca82592e699/28a9d669f0917d4e#28a9d669f0917d4e, you'll need to add this functionality yourself.

Once you have the Info tab of the Inspector in view (after pressing the left arrow 6 times), the button that clears a custom cue colour is "button 4 of window 1", so you'll need to build in a way of choosing "clear" in the initial dialog, test for that in the subroutine and then issue this command instead of the sequence that interacts with the Colors window:

click button 4 of window myWindow

It's not too onerous - but I'd do a bit of other tidying too: you don't need to check "UI elements enabled" _every time_ you process a cue (do it once outside of the subroutine), and you _never_ need to check for an OS greater than Panther since that's kind of a given with QLab 2...

Rich

Adam

unread,
Jul 25, 2011, 9:52:28 AM7/25/11
to ql...@lists.figure53.com
Thanks for the response Rich!

After going through the script the majority of the day yesterday, I
haven't found of way of inserting it into the script for it to work.
Would creating another subroutine work? Or, is there a current way of
easily putting it in the current subroutine? Trying to put it in the
list with the others just gives me errors because it can't reference
it in the color well, of course. And, putting it elsewhere in the
subroutine and trying to reference it above just tells me that my
reference is undefined. Is there a good script in the wiki you might
suggest that would be a good template to look at for trying to get
this script to work? I welcome any other hints or tips you might have.

For right now, I've copied the script and put the new parameters in to
engage the default in it's own script and that works just fine!


Thanks,

Adam

On Jul 23, 7:21 pm, Rich Walsh <richwa...@mac.com> wrote:
> On 23 Jul 2011, at 18:59, Adam wrote:
>
> > I've recently started using Stephen Swift's script for color coding
> > cues. However, I think it's missing one thing and I can't quite figure
> > it out. Is there a way to return the currently selected cue back to
> > it's color default?
>

> Assuming you mean this script,http://groups.google.com/group/qlab/browse_thread/thread/bf0eaca82592..., you'll need to add this functionality yourself.

Rich Walsh

unread,
Jul 25, 2011, 11:39:44 AM7/25/11
to Discussion and support for QLab users.
On 25 Jul 2011, at 14:52, Adam wrote:

> After going through the script the majority of the day yesterday, I
> haven't found of way of inserting it into the script for it to work.

1. Add "0 Clear" to the beginning of colorList:

set colorList to {"0 Clear", "1 Cantaloupe", ...

2. After:

if "Colors" is in (get name of windows) then
click button 1 of window "Colors"
end if

Add:

if myColor is 0 then


click button 4 of window myWindow

else

3. After:

click button 1 -- to close the Colors window
end tell

Add:

end if

I think that's it.

Adam

unread,
Jul 25, 2011, 1:54:48 PM7/25/11
to ql...@lists.figure53.com
Yup, that did it! Thanks Rich!

Next time I need to remember that the simplest way can be the one that
you want. But, I understand now what those new parameters are saying.


Thanks,
Adam

Reply all
Reply to author
Forward
0 new messages