Troubleshooting
Lemur downgrade to 4.1.2
Started by blingy on .
Sign in or create an account to join the conversation.
a quick playing around shows that tabs are actually a red herring. Ignore them. You can do a simple myX = Fixtures.T_Trigger.x;
You can test this by trying to create a fader with the same name in 2 different tabs - it won't let you (it renames the second one by adding a '2').
Opening up the .jzml shows that the faders are referenced off the Container name even though they are embedded inside the <WINDOW class="Tab"> ... </WINDOW> tags. I don't know if this is new or if it always was this way, but as of 5.0.3, Tabs are like the points on "Who's Line Is It Anyway?" - they just don't matter (for scripting).
You can test this by trying to create a fader with the same name in 2 different tabs - it won't let you (it renames the second one by adding a '2').
Opening up the .jzml shows that the faders are referenced off the Container name even though they are embedded inside the <WINDOW class="Tab"> ... </WINDOW> tags. I don't know if this is new or if it always was this way, but as of 5.0.3, Tabs are like the points on "Who's Line Is It Anyway?" - they just don't matter (for scripting).
Yup, and i can confirm it was always this way (well at least, from v4 and afterwards which is when I bought Lemur).
Tabs are not "included" per se in the project hierarchy.
Tabs are not "included" per se in the project hierarchy.