Schematic and pcb editor without screen leftovers when moving parts.
Alexander.
Schematic and pcb editor without screen leftovers when moving parts.
Alexander.
12
I don't consider language in a library to be a kicad bug.
This is a good idea.
Hopefully stuff will be fixed and optimized.
I use the kicad-product-r5640.
Quite happy about this version, but some things are really sluggish (part selection. switching canvas).
Build issue(?):
The development builds doesn't have a BZR number, or at least the one I use doesn't.
This can be found by looking in control panel->uninstall.
Windows installer:
Only main program (kicad.exe) and pcbnew is registerd on the start menu.
General:
(#2 on your list) When creating a new project the file kicad-dir/share/template/kicad.pro is copied to kicad-dir/noname.pro, this causes an error in windows since file writing is not normally allowed in "Program Files" (install to other folder works fine).
Also, this causes all you files to be named to noname.*.
For your list I have these comments:
3
Not entirely sure what you mean here.
Active libraries comes from the .pro file which is copied from the template upon creation.
IMO this is just fine, all libraries should be there by default, and you just remove the ones not needed for that project.
4
The save-as menu appears if you open eeschema directly, but not if you open it from a project.
It seems like this is a deliberate choice by the developers, why I have no idea.
6, 9, 10, 11, 18, 20, 23, 26,
This works just fine in my version.
12
I don't consider language in a library to be a kicad bug.
14
Moving components (M key) shouldn't preserve wires, use drag component (G key) to preserve connections.
15
Use delete node (no hotkey, should be backspace) to delete part of wire .
24
This is to be expected since the libraries is defined in schematic editor and stored in the .pro file.
Thanks for your post. I have incorporated your input and reposted the list. Also updated the spreadsheet.
The original list wasn't mine, but some items I found in this forum someone was complaining about KiCAD. I figured there were a lot of the items that would have been solved but hadn't had a chance to check them all yet (believe the person griping was using the latest "stable" build.
I tried kicad a few months ago, looking for an eagle alternative. My main qualm was the need to go through a schema export to start the layout. Why can't it has a single repository for the design and having both the schema and layout editors updating the same repository?
I decided to stick with eagle for now. Will sample kicad again next year.
traps: kicad[24070] general protection ip:7fd777d9f558 sp:7fffc80652b0 error:0 in libgobject-2.0.so.0.4400.1[7fd777d7e000+51000]
Any chance you can get a backtrace? Feel free to submit to the bug tracker.
I think that change was just committed yesterday or today. You will see it in the next stable release next month unless you want to check out the development branch today.
Did we mention proper clipboard (copy-paste) functionality?
Alexander.
I tried kicad a few months ago, looking for an eagle alternative. My main qualm was the need to go through a schema export to start the layout.
Why can't it has a single repository for the design and having both the schema and layout editors updating the same repository?
A schematic is the "source code" for a PCB design. Why you'd want to start laying out a board without a schematic is sort of crazy for anything other than the absolute most trivial design.
QuoteWhy can't it has a single repository for the design and having both the schema and layout editors updating the same repository?
Because one schematic can be used to make different layouts.
QuoteWhy can't it has a single repository for the design and having both the schema and layout editors updating the same repository?
Because one schematic can be used to make different layouts.
A repository can contain more than one layout. The design flow should be seamless, in both directions.
What do you mean by "repository?"
What do you mean by "repository?"
It can be implemented in many ways, for example a data file. The key point is that the user doesn't need to deal with import/export between the various steps of the design. They are all parts of a seamless design process.
Did we mention proper clipboard (copy-paste) functionality?
Alexander.
Can you expand on this? What are some scenarios you are looking to be able to do?