There is no builtin exporter for GenCAD which one of my vendors prefers (don’t ask - they get the job done). So I used the add Special:Execute Command dialog to do the equivalent. The command I entered was:
So it appears the path was a rathole. My problem is the with Output Path. It appears to be not a path but instead a filename. This file ends up in the jobset output directory (in my case ./Outputs). In this file is stored the output of the exectable.
I store the GenCAD data in a Outputs\GenCAD and sought to do this same for this log. However, it doesn’t appear to work. You can change the name to something more meaningful than it automatically generated if it is left blank. However, you can’t store it in a subdirectory. If you know a way, please enlighten me.
If you try this you will get an obscure error message complaining that it can’t create a file in the Appuser temp directory. Along the debug path, I confused my problem with finding the path to the CLI. Sorry for the distraction.
The jobset feature is new and seems to have some usability problems. You’re right, filename isn’t a “path” unless it includes the directory path. This should be changed in the UI, especially because it conflicts with other places where the term “path” is used.
Dealing with errors while running jobs is difficult or even impossible. I even got KiCad choked. And now I don’t remember how I did it…
There’s no any feedback of the state of running Output set (except that KiCad weirdly opens the schematic and PCB editors).
It’s also problematic that the working directory of Special:Execute Command is the project folder and not the output folder. I can’t find a way to know what is the current Output path of the Folder Output Options. Therefore I can’t for example manipulate files created by the running Output if I want the command to be re-usable in several Outputs. A temporary variable, like “${KI_CURRENT_OUTPUT_FOLDER}”, might do the trick (I see I can use variables inside commands).
Sorry, this because a random collection of findings.
