Eeschema 6.0.4
When printing to a file, the output path (once navigated) is remembered only until KiCad is closed, and then that path is lost; the next time KiCad is instantiated, the output path reverts to a default.
I don’t mind using the default filename “output.xxx”, but re-navigating to a remote network path/folder, which is a dozen layers down, is laborious IMO.
Good point.
That annoys me as well. In 6.0.4 it’s not even remembered between prints (Lubuntu). Every time tediously navigating to the desired directory is incredibly time-consuming.
Open a new issue on gitlab indicating the most recently used path in this case is not saved. These types of issues (especially MRU paths) are usually fixed very quickly once they’re reported.
It’s been this way for many years which means it was implemented a long time ago, and just never changed after that, and making an issue out of it on gitlab is a good start t bring some change in that regard.
I’d also prefer to have an initial default of the current project directory for this.
As “initial default”, please, and no “output.pdf” file name. Ideal would be that that last path is shown and the file name can be edited.
GitLab: no thanks… then I’d rather live with the current situation.
But perhaps the OP has the courage to enter the GitLab world of “streamlined user-friendliness”.
Ideally KiCad would get a default template (or multiple) project that can be edited and which is used to initialize new projects. Then you could set this also to your personal preference for all new projects.
Like most who use TLAs on a regular basis, I used it thinking I’d be understood, and in the circles I run in, ‘RFE’ is both a normal and expected usage for the expansion.
I forgot I was in Monrovia, when I am used to being in Spokane. Context switching isn’t always fast enough. As a newbie – here – I can expect a bit of slack to be cut.
I am not smart, and I finally got around to knowing this; it took a while.