[quote=“bobc, post:16, topic:8563”]
Here is my strictly unofficial, just for entertainment only …
[/quote] Then 4.1 will be the last v4 release. Very interesting because I’ll ask to my distribution (OpenMandriva Linux) developers to pack it.
I have several schematic done with v4 then I’ll keep on using it but I’ll try to use new libraries.
Then v5 RC1 seems not too far. I’ll see how to have both installed and working.
[quote=“bobc, post:15, topic:8563”]
I think that is unchanged in v5, there is a sort of workaround procedure (should be FAQ?)1. Open destination project2. Use “Append sheet” to copy sheet from source project3. Copy/paste within project4. If no longer needed, delete appended sheet
[/quote]Tried but it seems a bit more complicated. Given that is interesting but quite off topic I open a new thread.
Be aware that we are not quite finished with the reorganization effort. Take a look at the included ToDo.md file for details and look at the issues of the repo. (the todo list what old lib has been transferred already vs what is missing and the issues list the problems we found. Most problems are regarding the renaming of footprints and footprint libs.)
Are there plans to create a well-tested, illustrated, write-up for how this remapping is done? And post it on the KiCAD “Blog”, or some other very accessible, obvious, location?
When the new symbol management feature was announced on the Forum, the remapping process sounded rather involved and varied based on how you were using the library system. The complexity of the conversion process convinced me to stop using nightly builds, until release of KiCAD 5 (or at least until that release was imminent).
Officially, KiCad is in version 5 feature freeze. There are a few segfault bugs that have to be fixed before I will create a version 5 branch. This branch will become release 5-rc1. From that point on, the length of time it takes until the final stable 5 release depends on how quickly bugs are reported and all high priority bugs get fixed. I’m hoping to have the version 5 branch done before FOSDEM 2018 (February 3-4, 2018). If all goes well, a stable 5 release could happen sometime near the end of Q1 2018. As most things open source, it will be ready when it’s ready.
It’s worth pointing out that I’ve made this optional because it has some known performance issues for some people and some use cases that we’re not going to be able to fix in time. It’ll be disabled by default to avoid annoying too many people (as it’s hardly a critical feature), you’ll want to enable the last option here if you want it:
There are some other improvements to the symbol chooser that don’t involve footprints, which will still be there, but they’re minor. Of course they involved a total overhaul of the underlying code, but y’all won’t see that
Well, I don’t think it makes finding footprints any easier. The intent is for it to support a workflow similar to how other popular EDA packages work, where rather than matching symbols to footprints later, you place “components” with fully paired symbol+footprint already in library — KiCad actually does support that, but is missing some functionality that’d make it easier to use so I figured I’d fill that out a bit.
I’m currently working on a number of fixes for hi-dpi displays (think Retina) that will make it into v5, maybe worth adding to the list as KiCad is currently painful on my 4k display (even though I’m just considering them bugfixes rather than features).