Hi, How does KiCad decide when nets are connected in PCBNEW? It doesn't seem to be quite as simple as overlapping copper.
I have just had to move a number of components in a design (following a redefinition of the module origin). Despite replacing their pads (almost) exactly on the same traces, I end up with a large number of DRC violations. I guess I could make them go away by retracing several nets, but that would be too much work, so I'm left with a design that I believe is correct but that doesn't validate. Is there a way to help KiCad to recognise connections? Another similar situation I remember is when two traces on the same layer cross, they are not always counted as being connected. I guess copper fill zones have similar issues too. While on the wish list subject, I have a little list of suggestions... The ability to toggle display of individual layers would be very useful (or maybe I've missed a trick?) I'd like to make a suggestion for dealing with the logical problems that arise when duplicating circuit elements in PCBNEW. This is straighforward enough in SCHEMA, as the new parts are numbered automatically. PCBNEW, however, cannot number the copied components automatically (I think the original numbers are duplicated). I think it would be useful to use the following approach: - module copies should be given an undetermined part reference - implement an option to replace those modules with a defined part of the same outline in exactly the same position (currently I believe it is only possible to edit the module) - simultaneously remove that part from elsewhere on the board if it is already present (in the great big pile of parts to place, for instance). It would then be relatively quick to place and route one part of the the circuit, copy it and simply replace/place the copied parts as required. In LIBEDIT, a "Save As" button would help newcomers create new parts similar to existing ones. This is currently be done by changing the part name, but newcomers may not find this easily and they might be afraid that the old part will be destroyed (it certainly took me ages to work this out). A "Save As" button could essentially throw up the name-changing dialog, so I'm guessing it wouldn't be too hard to implement. It would give LIBEDIT a much more standard interface. I'd also suggest that if a module is loaded from a library (instead of from a board) then that library should be automatically selected for saving the part back to a library. It took me a while to realise that the reason I couldn't save a module back to the library was because I had to reselect the working library (I know, I'm stupid... But other users may be, too). Finally: I have really liked KiCad from the earliest days and use nothing else. I remember the dark ages without a complete, free EDA suite. I also really appreciate the very hard work that Jean-Pierre continues to put in (essentially alone?) Best regards,
