(2020-03-02, 17:25)N. W. Perry Wrote: Does it need to be in the same directory as the .jar file? (And does that .jar file have to be inside the Java Virtual Machines directory in the "innards" of my system?)Speaking for Linux/MacOS versions: if your starter file changes the directory to the one the jar-file is in, you have to put your LDInspector.ldi there. But if you set all Java-paths correctly (which I have no idea for MacOS), you may start LDInspector from any directory and have another LDInspector.ldi in each one. So it's up to your preferences: either change path to (any) directory or not, LDInspector will try to load it's configuration there. The time I had the Windows-test-machine, I couldn't get the batch file working successfully at the same time without parameters and with one or more parameters.
Maybe LDInspector could offer a command line option? Something like
Code:
java .... ldinsp.LDInspector -data PATH_AND_FILE.ldi
Shell I?