I’m learning how to make custom footprints. I am working in the Footprint Editor. I have created a local library for custom footprints. I’ve added the library with the Manager and and my library shows in the select active library table. I can then save my new footprint.
Now as I continue editing my footprint, when I go to save again the active library is forgotten and I must select it again.
I am using: Version: (5.0.0-rc2-dev-493-gd776eaca8), release build
Actually this seems to be a clear bug, I can replicate it.
Don’t set the active library.
Save a footprint. Select the library from the list.
Save the same footprint again. The previously selected library isn’t pre-selected.
You can set the active library from the toolbar button or from the File menu. That is remembered.
But the whole “active libary” idea is a burden of the past and could be disposed of. The last used library should always be preselected, or the library where the current footprint was loaded from.
As for now I actually think it works fine as it is. One can have ones own custom library selected as current library in the menus and still navigate to other libraries one want to copy footprint from to one’s own custom library and use a starting point for “molecular” parts etc., without changing current library away from one’s custom library. Using the export command will then have the custom library as default.
Perhaps in the future (v. 6+) one would want to make the process more similar to the one introduced for the symbol editor?
IIRC there has been discussion about something like that in the dev mailing list.
The problem which was described is that the library is forgotten altogether for one footprint between edit/save cycles. I have to select the library every time I save the footprint even within one work session. It’s like having only “Save As” without “Save” and being forced to select a file every time. it’s not about changing the library.
I was the original poster for this particular “quirk”.
I just installed the 4-29 version, followed the same steps that alerted me of the original issue and all works well. The Active directory is remembered.