Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
stacker:docs:batchapi [2017/03/11 01:32] rjlittlefield |
stacker:docs:batchapi [2021/06/21 15:25] (current) rjlittlefield [Overview] change Build number |
||
|---|---|---|---|
| Line 19: | Line 19: | ||
| - | The facility described here is current as of Zerene Stacker Version 1.02 Build T201001162110. It is intended for use only by advanced users and software developers. | + | The facility described here is current as of Zerene Stacker Version 1.02 Build T2021-05-28-1930. It is intended for use only by advanced users and software developers. |
| ===== The Batch Script ===== | ===== The Batch Script ===== | ||
| Line 49: | Line 49: | ||
| - | For Microsoft Windows, a copy of Sun’s JRE is included as files in the Zerene Stacker installation tree. The necessary command line is long and complicated. Fortunately, you don’t have to generate it from scratch. Whenever Zerene Stacker is launched from Window’s Start menu or desktop icon, a copy of the corresponding launch command is written into a file named ZereneStacker\zerenstk.launchcmd in that user’s %appdata% folder. What your launcher program should do is read that file, append whatever few arguments are needed for your situation, and use the result. | + | A copy of Sun’s JRE is included as files in the Zerene Stacker installation tree. The necessary command line is long and complicated. Fortunately, you don’t have to generate it from scratch. Whenever Zerene Stacker is launched from Window’s Start menu, macOS Launchpad, or some other icon, a copy of the corresponding launch command is written into a file named ZereneStacker\zerenstk.launchcmd in that user’s %appdata% folder. What your launcher program should do is read that file, append whatever few arguments are needed for your situation, and use the result. |
| - | For reference, a typical launch command looks like this (broken across multiple lines for clarity): | + | For reference, a typical launch command on Windows looks like this (broken across multiple lines for clarity): |
| Line 79: | Line 79: | ||
| - | Mac OS X and Linux require somewhat different launch procedures. Contact [[support@zerenesystems.com]] for details. | + | Launches on macOS and Linux have the same general structure as on Windows but differ in specific parameters. On macOS, a suitable command line can be obtained by launching Zerene Stacker from its icon, then looking in folder ~/Library/Preferences/ZereneStacker to find the file "zerenstk.launchcmd". On Linux, a suitable command line can be obtained by running the executable program ZereneStacker/ZereneStacker, then looking in directory ~/.ZereneStacker to find the file "zerenstk.launchcmd". (Note that directory ~/.ZereneStacker is normally "hidden" because of the leading dot in its name.) If this process does not provide adequate information, then contact [[support@zerenesystems.com]] to resolve any issues. |
| Line 191: | Line 191: | ||
| This is for a Zerene Stacker that is installed in Program Files and is currently being used by "username". | This is for a Zerene Stacker that is installed in Program Files and is currently being used by "username". | ||
| - | This command looks like complete gibberish. The trick to understanding it is to take it apart a bit at a time. | + | This command probably looks like complete gibberish. The trick to understanding it is to take it apart a bit at a time. |
| Everything up through the com.zerenesystems.stacker.gui.MainFrame was obtained by reading the file %appdata%\ZereneStacker\zerenstk.launchcmd (after successfully | Everything up through the com.zerenesystems.stacker.gui.MainFrame was obtained by reading the file %appdata%\ZereneStacker\zerenstk.launchcmd (after successfully | ||