Differences

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

--- macros:function_syntax [2017/10/29 16:26] – ↷ Page moved from function_syntax to macros:function_syntax icke_siegen
+++ macros:function_syntax [2018/08/27 17:14] (current) – ↷ Links adapted because of a move operation icke_siegen
@@ Line 8: / Line 8: @@
   * the function has a name, and most likely this name already describes (very briefly) what this function does. It is reasonable to assume that a function named ''delete()'' deletes something
-  * in our situation with hundreds of functions it's very helpful that functions are classified in [[:namespace|namespaces]]. Thus you immediately see the difference between ''playbacks.delete()'' - which probably deletes a playback - and ''fixtures.delete()'' - which probably deletes a fixture.
+  * in our situation with hundreds of functions it's very helpful that functions are classified in [[macros:namespace|namespaces]]. Thus you immediately see the difference between ''playbacks.delete()'' - which probably deletes a playback - and ''fixtures.delete()'' - which probably deletes a fixture.
   * by convention, each function is denoted by a pair of brackets, even if there is nothing in them. ''go()'' is a function whereas ''go'' is something else, but not a function.
   * most functions accept parameters (a.k.a. arguments) which tell the function what exactly to do, or with what to do it. In the above example of course we need to tell the delete() functions which playback or fixture exactly to delete. Hence we would write something like ''fixtures.delete(29)'' in order to have fixture no. 29 deleted. In this case, 29 is the parameter value.
-  * more generally, when describing a function's parameter, instead of the '29' you would want to denote something like 'Number of the fixture to delete, given as integer'. That's why in general descriptions we write not only the parameter (one word, maybe camelCase, which can be explained later), but also mention the [[:types|type]] of value which this function expects. For our delete-fixture-example we would write something like ''fixture.delete(Int32 fixtureId)'' as our fixture.delete function needs the id of the fixture-to-delete which must be an integer value.
+  * more generally, when describing a function's parameter, instead of the '29' you would want to denote something like 'Number of the fixture to delete, given as integer'. That's why in general descriptions we write not only the parameter (one word, maybe camelCase, which can be explained later), but also mention the [[macros:types|type]] of value which this function expects. For our delete-fixture-example we would write something like ''fixture.delete(Int32 fixtureId)'' as our fixture.delete function needs the id of the fixture-to-delete which must be an integer value.
   * if the function expects more than one parameter, the type/parameter pairs are separated by commas, like so: ''function(type1 parameter1, type2 parameter2, type3 parameter3)''
-  * finally, while many functions on Titan just do something (without letting you know), there are others which give back a value: the return value. Again in an attempt to do it as generally as possible, we always denote the type of return value before the function itself - and for those functions which do not return anything the type of the return value is [[:type:void]]. **When  putting such functions to use in a step, simply omit the 'void' keyword. In turn, functions WITH a return value are usually used exactly BECAUSE of this value, and used accordingly.**
+  * finally, while many functions on Titan just do something (without letting you know), there are others which give back a value: the return value. Again in an attempt to do it as generally as possible, we always denote the type of return value before the function itself - and for those functions which do not return anything the type of the return value is [[macros:type:void]]. **When  putting such functions to use in a step, simply omit the 'void' keyword. In turn, functions WITH a return value are usually used exactly BECAUSE of this value, and used accordingly.**
 Putting this to use we can now at least make something out of the above mentioned function:
   * ''Void ''  -- this function does something but doesn't return any value
-  * ''Group.StoreMenu ''  -- this is the namespace. Most likely this function is applicable in the Group Store menu (in [[:console_and_simulator|console notation]]: <Group> [Store] )
+  * ''Group.StoreMenu ''  -- this is the namespace. Most likely this function is applicable in the Group Store menu (in [[macros:console_and_simulator|console notation]]: <Group> [Store] )
   * ''StoreOnButton ''  -- this is the very function. Probably it stores something (a group, see the namespace) on a button.
   * finally, inside the pair of brackets, we have three pairs of type/parameter ''String group, Int32 index, AcwUserNumber userNumber''
-    * a [[type:string]] which denotes the group
+    * a [[macros:type:string]] which denotes the group
-    * an [[type:Int32]] which denotes the index (which exactly needs to be explained separately)
+    * an [[macros:type:int32]] which denotes the index (which exactly needs to be explained separately)
-    * and finally the userNumber which needs to be given as [[type:AcwUserNumber]] which probably is an [[type:object]]
+    * and finally the userNumber which needs to be given as [[macros:type:object:acwusernumber]] which probably is an [[macros:type:object]]
 If you want to cross-check: http://api.avolites.com/10.1/Group.StoreMenu.StoreOnButton.html
@@ Line 46: / Line 46: @@
 see http://api.avolites.com/10.1/Math.Cast.ToSingle.html
-All the Math.Cast functions do explicitely change a value's type , and hence, by definition, DO have a return value. This function takes an [[type:object]] as input (parameter), and spits out a [[type:single|single precision value]]
+All the Math.Cast functions do explicitely change a value's type , and hence, by definition, DO have a return value. This function takes an [[macros:type:object]] as input (parameter), and spits out a [[macros:type:single|single precision value]]
 ==== functions as parameter - nested functions ====
-The [[example:changexfade|example changexfade]] takes this a step further:
+The [[macros:example:changechaseroverlap|example changexfade]] takes this a step further:
   ActionScript.SetProperty("Playbacks.Editor.Times.ChaseFixtureOverlap", Math.Cast.ToSingle(1))
   * the **outer** function ''ActionScript.SetProperty'' sets a property, in this case the property ''"Playbacks.Editor.Times.ChaseFixtureOverlap"'', to a value
-  * in this case, this value needs to be a [[type:single]] - and our value '1' is NOT a [[type:single|single value]]
+  * in this case, this value needs to be a [[macros:type:single]] - and our value '1' is NOT a [[macros:type:single|single value]]
   * hence, we use this casting function ''Math.Cast.ToSingle''...
   * ... and use this function as **inner** function by putting it as parameter for the outer function
@@ Line 64: / Line 64: @@
   CueLists.GoBack("Location=Playbacks,2,1")
-See [[example:cuelistgoback]]
+See [[macros:example:cuelistgoback]]
-At first glance this looks like more parameters in the brackets - but it isn't. The commas are inside the double quotes which make the entire part one string: ''"Location=Playbacks,2,1"''. And the function definition shows that this is a [[type:handle]].
+At first glance this looks like more parameters in the brackets - but it isn't. The commas are inside the double quotes which make the entire part one string: ''"Location=Playbacks,2,1"''. And the function definition shows that this is a [[macros:identifier:handle]].
 ----