Cue Target Naming

[Alexander (Mailing List) Taylor]

Hello,

I'm wondering if it's possible to have the Target of a cue displayed in dot notation. For instance it would be [Cue List].[Group].[Sub Group].[Cue Name]

Right now, I'm finding larger workspaces get very confusing since cue names aren't unique. If we could display them in this way (maybe a switch in Preferences) it would be very useful to me. Does this make sense to others?

Thanks,
Alexander


The Right-To-Know Law provides that most e-mail communications to or from School District employees regarding the business of the School District are government records available to the public upon request. Therefore, this e-mail communication may be subject to public disclosure.

[talkingtobrian]

Wow, that's a really great idea. It would certainly solve something that has been unconsciously bugging me while I teach my students.

[Brad Lawryk]

That's pretty much what I do now with the only difference is I use dashes instead of periods. I didn't know periods didn't work as I prefer the dashes as they are easier to see.

[Alexander (Mailing List) Taylor]

Yes, the delimiter doesn't particularly matter to me, though the programmer in me likes the periods.  My question was more geared towards if this could be an option that was integrated.  Keep the actual cue names short, but the option to show the full path on the targets (or maybe even a path column option).  So you can see where things are/go.

Alexander

-- 
Contact support anytime: sup...@figure53.com
Follow Figure 53 on Twitter: http://twitter.com/Figure53
--- 
You received this message because you are subscribed to the Google Groups "QLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qlab+uns...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/63b4b407-3343-4b82-bcc3-427ec748453b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Rich Walsh]

I’m not sure I fully follow as I think you keep switching between “cue name” and “cue number”, but if you mean you’d prefer example B to example A in the attached screenshot then you could write something to update the Start Cues (etc) you want to appear like this on a hotkey, eg:

tell application id "com.figure53.QLab.4"

tell front workspace

repeat with eachCue in (selected as list)

try

set eachTarget to cue target of eachCue

set cueListDetector to cue id "[root group of cue lists]" -- Cue lists have this as their parent

set pathList to {}

set eachParent to eachTarget

repeat until eachParent is cueListDetector

set end of pathList to q number of eachParent

set eachParent to parent of eachParent

end repeat

set currentTIDs to AppleScript's text item delimiters

set AppleScript's text item delimiters to "."

set pathText to reverse of pathList as text

set AppleScript's text item delimiters to currentTIDs

set eachType to q type of eachCue

set eachTypeLowercase to do shell script "echo " & eachType & " | awk '{print tolower($0)}'"

set q name of eachCue to eachTypeLowercase & " " & pathText

end try

end repeat

end tell

end tell

You could tweak it to include the target cue’s name too. You’d just run it on the cues you want to override the default naming for.

Rich

[Alexander Taylor (Mailing List)]

I don’t see where I mentioned cue number at all, I was referring exclusively to cue name and the target of said cue.

What would be ideal, is if the start cue was named start “You know my name” but the target could be switched between the cue number 1, and the path Cue List. . .You know my name - that example fell apart when I realized you hadn’t named your groups, just numbered them.

This is what I made yesterday that caused me to write this email.  I name each cue list, then each group, all the way down the line.  Makes it very easy to see what’s going where.  If this was built in so you could display a target by the path, you could keep a nice short name, but see where it’s going.

Alexander

--
Contact support anytime: sup...@figure53.com
Follow Figure 53 on Twitter: http://twitter.com/Figure53
---
You received this message because you are subscribed to the Google Groups "QLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qlab+uns...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/E75771AF-3563-4ECA-B706-8BE527407067%40mac.com.

For more options, visit https://groups.google.com/d/optout.

<Screen Shot 2017-05-26 at 01.51.33.pdf>

--
Contact support anytime: sup...@figure53.com
Follow Figure 53 on Twitter: http://twitter.com/Figure53
---
You received this message because you are subscribed to the Google Groups "QLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qlab+uns...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/E75771AF-3563-4ECA-B706-8BE527407067%40mac.com.

[Rich Walsh]

I think it’s because the Target column shows cue number (unless there isn’t one), presumably precisely because cue number has to be unique and to show anything else is going to be confusing… So I thought you were talking about cue numbers.

I’ve never used cue targets without numbers on the targeted cues for exactly this reason – and also because you can set the target by typing the number and not have to drag cues around. I have a very simple naming convention: on the show I was fiddling with last night, resets are 6xx, QDisplay cues 7xx, MIDI cues 8xx, MSC for video 9xx, and so on. It would be easy to extrapolate that to a nested numbering structure – and use the existing tools to have the unique cue numbers that appear in the Target column take the form you want.

I think I now understand that what you’re asking for is that if there is no cue number then QLab construct a string showing the “path” to the cue (constructed from the names of its ancestors) rather than just its name, as that is more likely to be useful for identifying the cue than its name alone. Wouldn’t "/" be the more obvious delimiter then? “.” can be used in MSC so often turns up in cue numbers, which I would find confusing. Maybe “ > “?

Rich

On 26 May 2017, at 03:52, Alexander Taylor (Mailing List) <alexand...@orol.org> wrote:

I don’t see where I mentioned cue number at all, I was referring exclusively to cue name and the target of said cue.

What would be ideal, is if the start cue was named start “You know my name” but the target could be switched between the cue number 1, and the path Cue List. . .You know my name - that example fell apart when I realized you hadn’t named your groups, just numbered them.

This is what I made yesterday that caused me to write this email.  I name each cue list, then each group, all the way down the line.  Makes it very easy to see what’s going where.  If this was built in so you could display a target by the path, you could keep a nice short name, but see where it’s going.

<PastedGraphic-1.tiff>

[Alexander Taylor (Mailing List)]

Yes, your last paragraph is what I’m getting at.  I chose . because that’s what is used in domain names and programming.  Would make just as much sense to be /, though it might be good to keep it independent from what OSC and the like use.  I know it’s a fringe case, but for most of my cues I don’t want any number so it can’t be externally controlled.  Only controllable from the logic in the workspace, with cues triggering other cues and the like.  I could see where it shows the path or the number  (if present).  Might be a good way of doing it.

Alexander

-- 
Contact support anytime: sup...@figure53.com
Follow Figure 53 on Twitter: http://twitter.com/Figure53
--- 
You received this message because you are subscribed to the Google Groups "QLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qlab+uns...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/C5F5731F-1209-4987-ADD4-0124FBB2A37B%40mac.com.