The OCE option has now been removed.
Quoting Seth (https://www.mail-archive.com/kicad-developers@lists.launchpad.net/msg39763.html):
Previously, KiCad had default paths for schematic symbols in
/usr/share/kicad/libraryand for footprints in/usr/share/kicad/modules/(Windows users found these at %{KICAD_PROGRAM}\share\kicad\library and %{KICAD_PROGRAM}\share\kicad\modules)Starting with tomorrow’s nightly build, we will be installing these to
/usr/share/kicad/symbolsfor schematic symbols and/usr/share/kicad/footprintsfor layout footprints.
Depending on your setup, this may require some manual intervention after an update. New installations should work by default.
2 Likes
As part of a general cleanup to the UI of the Create Array... tool, a new option has been added that automatically assigns the next available reference designator to the newly created footprints (it works in the same way as Paste Special... -> Assign unique reference designators)
The cleanup was mainly to remove the clutter in that dialog when running from the board editor: none of the pad numbering options were relevant.
The way it should work is that if you have a block to array like below:
J1 J2
J3
It will create an array with the reference designators something like below (dependent on other footprints on the board not having those reference designators already)
J1 J2 J4 J5
J3 J6
J7 J8 J10 J11
J9 J12
A possible workflow for getting this working would be:
- Ensure that the schematic and the PCB are synchronised before starting.
- Use the array tool on a set of components of the PCB.
- In the schematic, copy the same block of components and do
Paste Special... -> Assign Unique reference designators(they will need to be pasted as many times as required). - Finally the components in the schematic and PCB can be linked up with a
Update PCB from Schematic... (F8)selectingRe-link footprints to schematic symbols based on their reference designators.
This option should be available in the next nightly run.
Ref commit: https://gitlab.com/kicad/code/kicad/-/commit/a79a2212573ab001402b01dcd2bf7a71ecc376cd
5 Likes
Cool! I’ve been waiting for something like this for years!
1 Like
Until now, CTRL + E could be used to open the editor of the current symbol or footprint (below the mouse).
Since yesterday, CTRL + SHIFT + E can be used to open the symbol or footprint it in the library editor, instead of editing the current symbol / footprint.
Thanks Seth! https://gitlab.com/kicad/code/kicad/-/issues/9454
4 Likes
We finally got some information about the v6 release schedule! Quoted from Wayne’s message, https://www.mail-archive.com/kicad-developers@lists.launchpad.net/msg39781.html :
- Tag RC1 on November 15.
- 6.0.0 release announcement December 31 (maybe the day before Christmas
just for fun).
15 Likes
The annual stable release policy sounds exciting.
https://dev-docs.kicad.org/en/rules-guidelines/release-policy/
2 Likes
The Plugin and Content Manager has been enabled by default and will start showing up in nightlies tomorrow.
There is work-in-progress documentation aimed at plugin/content creators on the dev docs site. Adventurous plugin authors can already start submitting their work to the official repository by following the guidelines there (take a look at the things already in the repository for examples).
There are some things to be aware of when testing:
- Uninstalling a color theme using the PCM does not remove the theme. This is by design currently, but we’re looking at ways to improve this UX.
- If you have a saved size of the KiCad project manager window (i.e. if you have run KiCad before), the saved size will not be updated now that this is turned on. So, the button for the PCM may appear off-screen and you may need to manually make the KiCad manager window larger. This should not affect new installs.
13 Likes
I am really happy to see PCM in KiCAD! However, I am worried about the plugins’ future in KiCAD 6. In the current nightly, there is API regression that affects several plugins in such a way they stop working. And without fixing the API, they will not be available for v6.
Could you provide updates on the Python API v6? I raised my concerns on the mailing list about a week ago, but I received no response from the developers (see https://lists.launchpad.net/kicad-developers/msg45379.html). The regression was reported about 9 months ago and we were asured that it will be fixed before release. However, I am really getting worried as it is 7 days until RC.
I have a question regarding PCM - what about plugins that have third-party dependencies (i.e., Python libraries). Does the installation process via PCM takes this into account? Currently, it doesn’t look so. Is it expected that the user will have to install such dependencies manually?
1 Like
Can’t you just include all dependencies in the plug-in? The website linked above states that
The contents of the
pluginssubdirectory should include any Python source files and resources required by your plugin
1 Like
Could you start a new thread please? This one is really just for announcements and gets impossible to search if every new feature is discussed within it.
2 Likes
Here you go: Plugin and Content Manager - how to handle plugins with dependencies?
However, I didn’t notice there is such a rule. And short discussions happened here before and none was complaining.
Some things die off on their own after a few posts. Some have the potential to go on longer. Sometimes a new topic will simply get better visibility.
1 Like
When KiCad V6 is released I think it’s a good idea to start a new topic for it and then only give a limited amount of people access to add posts.
Comments and questions can than easily be handled by starting a new thread and referring to the “list of new features and development news”
7 Likes
It’s been in for a bit but probably worth a mention: The routing corner style (Ctrl+/) now has 4 modes to cycle through: 45-degree, 45-degree with rounded corners, 90-degree, and 90-degree with rounded corners. The active corner style is shown in the message panel at the bottom while routing.
corner_modes
22 Likes
Sad news for those who have waited for the new python API. In Python API status in v6 we have been told that it’s not ready yet for v6 RC or relase and will be postponed. Existing plugins should be converted to the changed old style API to work with v6. There will be no eeschema API in v6. More details and discussion in the linked thread.
Any way of changing the corner radius ?
The router operates in a fixed-angle mode, not fixed-radius. You set the radius by where you click. Fixed-radius curves can be added using the Fillet Tracks post-processing operation.
1 Like