Support Forum

Macro headers and system variables in Windows

User
LayoutEditorFull
Sunday 14th October 2018
I observe that the macros and other such things, have a C-like header which is obviously meant for a UNIX filesystem: #!/usr/bin/layout #name=layer setup macro #help=setup macro automatically generated at Fri Oct 12 2018 So for WIn10, some obvious questions... 1) Does the header actually matter, to anything? If so, to what? 2) If the header matters, should it be changed to (say) C:\Program Files (x86)\LayoutEditor\bin\layout.exe ? Or with forward slashes? 3) I see some other macros which look like they use system variables. Windows is kinda craptastic in regards to the shell and variables. Would it be sensible to make use of Windows shell and variables? In the interests of setting up a design management environment, would perhaps a .bat "launcher" which sets needed (?) vars and then invokes layouteditor.exe with all the paths and vars set, maybe be a good way to force everything to start in a known clean state? Maybe in conjunction with the "bundle" data scheme?
J├╝rgen
LayoutEditorFull
Sunday 14th October 2018
The macro header is used to identify a file as a macro. The first line of the macros will enable to start the macro directly on Linux system and Mac OSX. This will not work on Windows. So it make no sense to adjust the first line for Windows system. You can start a macro by using the macro file name as command line parameter. This will have the same effect as calling the macro directly on Linux/Mac. It can be used to to adjust setting, but it makes no difference that setting up a autostart macro.