Differences

This shows you the differences between two versions of the page.

--- macros:identifiers [2017/11/22 11:38] – ↷ Links adapted because of a move operation icke_siegen
+++ macros:identifiers [2018/06/19 15:30] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 ====== Identifiers ======
-One of the most common - implicit - tasks is to identify handles: you need to tell Titan with which handle it is to perform an action, e.g. which handle to copy, which cue to jump to, which cuelist to advance, which chaser to stop. Depending from your needs this can be done in a few ways:
+This is a very special section: 'identifiers' tries to list and explain all the values you need to identify a certain item or state. As such, 'identifiers' are not part of pure programming logic or documentation. In fact in most parts this is just convention and system design: how to identify a certain button/playback/palette, how to tell which state a certain item to set to, etc.
-  * by user number: since all items get their unique user number, you can use this as identifier. Identifying is then: give the scope, give the user number. Like: fixture #3, palette #7, macro #28.
+Identifiers may be of various data types: there may be very complex ones, e.g. [[macros:identifier:handle]], and there are others which are simply a string or even a number which you only need to know and set as argument for a specific function or variable.
-  * by titan ID: every single item within Titan has its unique id which can be used as identifier. This is good, as this is just one number, nothing more. But the problem is: most user numbers are assigned by ransom, and will be different in each showfile. There are only few exceptions from this: the masters which you can assign have reserved titan IDs, see [[macros:identifiers:titanid]]. Another exception is if you do not need to explicitely know this ID, but simply want to pass it as argument: find a function which gets this ID and use this function as argument.
-  * by location: this is like saying 'the 3rd button in the Playbacks window' or 'Playbacks Page 3 Fader 4'. For this it is important to know the exact syntax, as well as the available handle groups. E.g. the handle ''"Location=Playbacks,2,1"'' translates to 'Playbacks, page 2, 1st playback' - this is the 'real' fader playbacks (see [[macros:example:cuelistgoback|]]).
+Identifiers listed here:
+<nspages macros:identifier -h1 -simpleList -textPages="">
+----
+~~NOCACHE~~
+{{page>macros:formats_and_syntax#further_readings}}
+~~DISCUSSION~~
-tbd Groups of Handles