AVOSUPPORT

User Tools

Site Tools

Trace:
macros:recorded_vs._coded_macros

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
macros:recorded_vs._coded_macros [2017/11/24 10:44] – [Limitations] icke_siegenmacros:recorded_vs._coded_macros [2017/11/28 15:24] (current) – icke_siegen
Line 145: Line 145:
  
 1. "Next fixture" might work as ''Selection.Context.Global.PatternNext()''\\ 1. "Next fixture" might work as ''Selection.Context.Global.PatternNext()''\\
-2. "at full" is not that easy - we were discussing how to set attribute value the other day\\+2. "at full" needs to be discussed separately - setting an attribute uses the function [[macros:function:Programmer.Editor.Fixtures.SetControlValueById]] and goes along the lines Olie outlined [[http://forum.avolites.com/viewtopic.php?f=21&t=5189|in the forum]]. Another option is literally using ''@@'', by  ''Command.RunCommand("@@")'', see [[:macros:function:Command.RunCommand]] \\
 3. "append step" is the most tricky part: the function could be ''Playbacks.AppendCue(Handle handle)'' - but this would require us to know the handle \\ 3. "append step" is the most tricky part: the function could be ''Playbacks.AppendCue(Handle handle)'' - but this would require us to know the handle \\
 4. "at 0" -> see above 2.\\ 4. "at 0" -> see above 2.\\
macros/recorded_vs._coded_macros.1511520270.txt.gz · Last modified: 2017/11/24 10:44 by icke_siegen
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki