Post-v5 new features and development news

Seeing as it seems v6 will have something like a stackup planner will that also mean that things like per layer length tuning and node-node resistance measurement might be a thing. Or no real interest?

There’s a new color theme editor:

You can now place multiple color theme files in the colors folder inside your user settings folder (there’s a handy button to open that folder, too). You can get these theme files from something like Thomas’ repo, which has been updated to include JSON versions of the themes that are compatible with the latest nightlies, or you can create your own!

The color theme editor lets you create new themes inside KiCad. You can copy/paste colors between slots (just right-click a color button), reset one or all colors to KiCad default values, and see a live preview of your changes right inside the preferences window.

There will always be a theme called “User” that reflects whatever your existing color settings were before this feature was released.

Note: the live preview currently doesn’t show all types of items. I wanted to get this out for people to play with at this point, even though it’s not completely finished.

Along with this comes some other related new features:

  • LibEdit can now optionally use a different color theme than Eeschema (configure this in LibEdit preferences)
  • Plotting in Eeschema can now use a different color theme than the main window, and you can plot background colors to PDF, SVG, and PS files. Configure this in the Plot Schematic dialog:

Please report bugs if you find them! I’ll be expanding this to support the other applications soon, but it should already be working well enough to use on the schematic side.


For “per layer length tunning” you could modify my Length stats action plugin to report length of tracks on each layer. It is not exactly what you want, but it is something.

As for the “node-node resistance measurement” use pad2pad distance action plugin. It also reports cumulative resistance assuming 35um layer stackup excluding via resistance. Note that it calculates distance/resistance on tracks only. If you have a zone somewhere this is not taken into account.

1 Like

Could a moderator move the discussions about DRC to a new thread?

1 Like

Moved DRC discussion to a new thread

1 Like

Thanks David. Here’s the original message by Jeff:


This doesn’t work perfectly yet, there are problems with checkboxes and visibility. But the crashes which happened with the first iteration have been fixed.

1 Like

I believe the issues with the checkboxes and visibility (on MSW) were recently fixed. So if anyone is still getting them with a current nightly please let me know (or log a bug).


More hotkey definitions available for the 3D viewer. Shared commands (such as zoom in, zoom out) also now respect the hotkeys set for the rest of the suite.

1 Like

4 posts were split to a new topic: Using 3d models as a replacement for the DRC courtyard check

Hopefully, the resistor calculator will be merged for V6

Really useful, nowadays I still use some personal Python / Matlab algorithm to this work.
Propose, if it is not already done: could have a button in each option line to “place” the calculated configuration. The focus change to Eeschema and the cursor will place the configuration with the connection (as happens with the parts).
Other idea: in the log write the maximum and minimum value reached with the resistor-solution and the nominal tolerance selected.

Something like this where it can find optimal resistor values from the e12/e24 series for a voltage divider would be my suggestion for a resistor tool.

Nice tool, this web site.
The “resistances to divide a voltage (to branch a current)” could use the maximum power rate desired to each resistors.
I think, when @janvi is release and tested for us. We could write some “improvement request” at Gitlab group.


The first version of my altium board importer was merged.


10 posts were split to a new topic: New string replacement options for kicad assets

Sadly the forum does not support duplicating a post so here the original comment by @JeffYoung that i moved to its own thread as it sparked a discussion.


Does anybody know if the new schematics format being introduced these days also includes cache of used symbols in the same file, or is this yet to be changed?

1 Like

3D model “preview” flag changed to “show” flag (and persisted in files). See Footprint Properties > 3D Settings.


Did I ever announce sub- and superscript for Eeschema? Use ‘^’ to signal superscript and ‘#’ to signal subscript. (You have to turn processing on in Schematic Setup since I didn’t want existing schematics to be reformatted.)

I’m not sure superscript is really that necessary, but subscript is used a lot by some.


Hmm, ‘_’ is a more common notation for subscript (see LaTeX etc). Is there a reason this wasn’t used/is it too late to change?