User Tools

Site Tools


macros:function:patch.repatch.repatchselectedfixtures

Differences

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

Link to this comparison view

macros:function:patch.repatch.repatchselectedfixtures [2025/04/29 09:42] – created icke_siegenmacros:function:patch.repatch.repatchselectedfixtures [2025/04/29 12:49] (current) icke_siegen
Line 10: Line 10:
 ^ parameter | forcePark ( [[macros:type:Boolean]] ) : whether to park conflicting fixtures | ^ parameter | forcePark ( [[macros:type:Boolean]] ) : whether to park conflicting fixtures |
 ^ return value | [[macros:type:void]] |   ^ return value | [[macros:type:void]] |  
 +
 +During the discussion re. [[macros:example:repatchselectedfixtures|]] Gregory explained:
 +
 +> The **RepatchSelectedFixtures** function processes fixtures in the selection order, if you use groups to select the fixtures this should be something to be aware of. Partially because of this I also set the **Patch.Repatch.BunchUp** property to **BunchUp** since with the group I was trying (201: All MegaPointe in a copy of the demo show) it failed as it was attempting to repatch to a negative DMX address. I assume this was because higher DMX addresses appeared in the selection before lower ones however I didn’t look into it in detail. In principle **RetainLayout** would be fine to use but you do need to ensure that the specified DMX address and selection order are valid for what you are trying to do.
  
 == Example in ==  == Example in == 
macros/function/patch.repatch.repatchselectedfixtures.1745919747.txt.gz · Last modified: 2025/04/29 09:42 by icke_siegen

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki