Differences

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

--- macros:function_syntax [2017/10/29 16:35] – ↷ Links adapted because of a move operation icke_siegen
+++ macros:function_syntax [2018/08/27 17:14] (current) – ↷ Links adapted because of a move operation icke_siegen
@@ Line 18: / Line 18: @@
   * ''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 [[macros:type:string]] which denotes the group
     * 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 [[macros:type:acwusernumber]] which probably is an [[macros: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 50: / Line 50: @@
 ==== functions as parameter - nested functions ====
-The [[macros: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))
@@ Line 66: / Line 66: @@
 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 [[macros: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]].
 ----