Version: (5.1.5-0), release build
Platform: Mac OS X (Darwin 16.7.0 x86_64), 64 bit, Little endian, wxMac
When Quitting the Stand-Alone PCBnew, I get this error.
I open KiCad first, then open PCBnew (stand-alone). It boots and I can use it. But, when closing/exiting it, the error happens.
Not really a problem (yet) as I’m doing my work from the main gui panel.
This post is, in part, to fulfill the requirements of posting to enable ability to upload KiCad files (Trust Level -1).
FYI - Read & Write is enabled. I did setup custom file and folder locations when setting up KiCad.
All my stuff (Projects, Libraries… are on the Path and all is working well, except as noted above).
The “fp-info-cache” file: It’s not clear to me which one is the problem as there is one of these files in each Project folder.But, when using the Stand-Alone (i.e., no projects open) I see no related fp-info-cache file…
How are you starting pcbnew standalone? By clicking on an icon? Is it possible the launcher changes directory to one where you don’t have write permissions before running the application? Are you able to check the launcher properties?
[SOLVED - Sort of…] Discovered that if I create a PCB and Save it, no Errors when exiting.
That implies a User cannot run PCBnew and decide to not do any work, and exits. Then it will Error.
Might call it a Bug…
Thank you for responding…
I boot KiCad (main panel opens with last opened project).
Double-Click (or Right Click) on PCBnew in root folder where it resides (not a shortcut/alias).
PCB opens.
When exiting, error occurs.
(GIF video attached)
The PCBnew that runs from within the Main Panel shows One Icon at it’s top left corner (image below). Whereas the PCBnew booted from it’s root folder show Two Icons in top left corner and loads the full layer list versus my customized layer list.
So, you start the KiCad main program (which opens the .pro project files). Normally one would launch PCBNew from there. But instead you are then launching PCBNew from Finder (I have just barely enough MacOS experience to know that is called “Finder”) and in that Finder-launched process is where you have the issues.
Have you tried launching PCBNew from Finder without first launching the main KiCad project manager program? I’m wondering if there is some OS level resource locking that is happening if instead of launching PCBNew from the KiCad project manager (which would keep track of child processes) you launch PCBNew as a completely separate process tree. Or, I could be barking up the wrong tree with my limited knowledge of how MacOS does things…
I read all the doc’s and was able to figure out the ‘best’ approach to running PCBnew as stand-alone.
It is True PCBnew (and Eeshema) can be run as Stand-Alone app’s. Clearly pointed out in several doc’s. Also pointed out is info related to setting up the related Cache files.
Basically the trick to running PCBnew as stand-alone (from the install App/dir) is to Save the .pro - I was simply quitting it without saving the .pro.
After saving .pro, PCBnew closes properly.
And, ‘Yes’ while it may be the same PCBnew that runs from the Main Panel, it still presents the Toolbar Icons differently, as noted in previous post.
That’s good because they enable starting/opening boards without needing a project opened and having schematic/other when not wanted…
If you want to import multiple pcb files from different projects to build up a panel, launching PCBNew as stand-alone is one of the few ways to do that.
But, if you want integration from schematic to pcb (and vice-versa) for quick netlist updates from the schematic, or to highlight on the schematic where the component that you click on in the PCB is, you have to launch PCBNew and EESchema from the project manager to set up the inter-process communication.
