On Wed, 2009-10-28 at 00:33 +0100, Stefan Salewski wrote: > On Wed, 2009-10-28 at 00:25 +0100, Stefan Salewski wrote:
PCB gets quite slow when processing very long action scripts (lots of elements). There is a linear search executed O(n) complexity, n times. So O(n^2). Not ideal! I mentally noted the issue when I saw it, but there have been bigger issues to fix. Anyone interested in making an element-name hash table / btree in PCB? Even maintaining a sorted list would be useful - as we could then use a binary search. > Warning! Net "unnamed_net385" is shorted to net "unnamed_net270" > Warning! Net "unnamed_net385" is shorted to net "unnamed_net264" > Warning! Net "unnamed_net385" is shorted to net "unnamed_net261" > Warning! Net "unnamed_net385" is shorted to net "unnamed_net284" > > Sure, the pins overlap. Yep - that is pretty useless, but it isn't easy to do better. I guess we could have xgsch2pcb make PCB auto-disperse the elements (if starting from a blank board). I wouldn't want to do this when adding a few new items to an existing board - but then the current behaviour of lumping them all in a corner isn't exactly helpful either! What I want to have eventually, is a "parts bin" window, where all the parts yet to be placed are available. The user can then pick them up just like out of the footprint library. Bonus points for being able to multi-select, and hit "auto-disperse selected" in the parts bin. Filter by name, by footprint (leave all those decoupling caps to last etc..)... Anyone want to code this?? Best wishes, Peter C. _______________________________________________ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user