@hildogjr, I can’t reproduce the deleted line segment issue, but I’ve fixed the undo issue.
Thanks. I will test again (tomorrow) and, if still, rise an issue on Git.
Editing here for track: https://gitlab.com/kicad/code/kicad/-/issues/4766
Doesn’t really work from PCBNew. If you probe from EESchema everything acts as you would expect it to. If you probe from PCBNew it doesn’t zoom (it zooms out all the way regardless of your selection on zoom) and doesn’t really center (it does move the screen but definitely not to the center)
Hi everyone, please do not report bugs or request features in this thread
Now it’s in the layout editor, too.
And before someone asks - see https://gitlab.com/kicad/code/kicad/-/issues/4742 if you want rounded corners.
EDIT: BTW, also pads can be edited with this tool:
Jon announced New project file format. It implements several wishes, at least:
- file extension
- separating non-board information (no more UI state in VCS!)
It also removes the old backup system. See the details in the dedicated thread.
The status of python2/3 especially on Windows has been problem for some time. The developers know very well that using python2 isn’t any good. The reason why the Windows installation is still python2 only is that one programming library project which is required by KiCad for full functionality doesn’t support their python3 version for mingw, the compiler environment currently used for compiling KiCad on Windows.
Seth asked help for solving that situation in the mailing list, see https://lists.launchpad.net/kicad-developers/msg44132.html. Help if you can, and let’s hope we can soon move to python3.
There is a new command in pcbnew, Move with Reference. This allows you to first pick the reference point for a move before the move starts. There is no hotkey for this command by default, but if you like this behavior (like me), you can reassign the default M
hotkey from Move to Move with Reference.
2020-07-06 19-36-18
There is a new automatic project backup feature:
- Enabled by default, can create backups every time you save a file
- Optional creation of backups when auto-save is triggered (disabled by default)
- Limit on total number of backup files and total backup file size
- Limit on number of backups to keep per day
- Setting for minimum backup interval (for example, if you like to hit Ctrl+S every 10 seconds but don’t want a new backup file every time)
How does it handle schematic files which are not in the project folder or its sub-folders? Is there a possible collision when two projects are using the same schematics file?
It does not, same as the existing project archiver (which uses the same code). Schematics must be included in the project folder (or a sub-folder of it) to be backed up.
Thanks to Jon, we can now hide ratsnest lines for a net. Select a board item belonging to a net (most often this would be GND or some other ubiquitous net which makes it difficult to discern other nets). Open the context menu and you’ll see Net Tools and can hide/show the selected net.
There’s also some backend support for coloring nets, but there’s no GUI yet.
EDIT: I created a new thread New Net Tools in pcbnew 5.99 because I can foresee this will raise comments, questions and feature requests.
Small warning: I didn’t post about this yet because there may still be a bit of churn in how exactly this works. It should be safe to play with though
Net Classes can now be assigned in Eeschema. They can also be used to color/style the wires & busses of a net. (And of course they feed through to PCBNew Net Classes.)
Will the Backup exclude other ZIP files to prevent ever expanding ZIPs?
Yes. In fact, there is a fixed list of file extensions that will be backed up: https://gitlab.com/kicad/code/kicad/-/blob/master/common/project/project_archiver.cpp#L157
Will it be possible to display the net names on the schematic or just assign them? Could you automatically just apply labels as net names?
I’m not sure I’m following. Net names are already applied by labels.
Net class assignments are what’s new. Net classes are normally applied to more than one net name.
We’ve talked about how to visually indicate net classes on the schematic.
- The current way is to use the net class colors and line-styles. Negatives are that they might not work well for very large netclass sets; positives are that they appear in plots, print-outs, etc. and have historical precedent.
- We could also support annotations (like the net names shown in PCBNew). Positives are that they’re easy to turn on/off en masse; negatives are that they won’t appear in plots, print-outs, etc.).
- We could have a mechanism similar to labels. Positives are that their placement, orientation, etc. is under the control of the author; negatives are that they’re harder to edit en masse and they can be visually noisy.
I’d love it if we could get by with just (1), with a slight preference for (1) + (2) if we can’t. I think Jon has a preference for (1) + (3).
It’s now possible to create a new net in pcbnew with Inspect -> Net Inspector. It can then be assigned to a pad in the pad properties. The change can also be fed back to the schematic with Tools -> Update Schematic from PCB (with more or less success).
This is an answer to long standing need for easier PCB-only design (WireIt plugin has been used for it).
Again, I opened a new thread for discussion: Creating nets in Pcbnew (5.99).