Indeed. I’ve had geographical annotation in c++ working for some time now. Having different commands in PCBNew and eeSchema could lead to all sorts of nightmares. During testing I found myself with “half done” projects where I had inadvertently got the annotation on the PCB and schematics out of synch. This is a complete nightmare to fix even on a small board. In fact the reason I started the work was because geographic annotation is a huge amount of work manually and back annotation is not just a lot of work but really easy to screw up.By having a single integrated tool analogous to “Update PCB From Schematic” can ensure coherency. From: Alexander Shuklin Well, I cannot make back annotation in python, it has to be c++. Actually that's why I jumped on that problem. Because once it's done you can use python for geometrical annotation. Actually I've seen python script to do that, but it parses sch file like plain text, which is bad. Python scripts can do powerful job, and as I see, some very uncommon stuff better to have as python plugins, and something general in standard GUI. I would say that geometrical annotation is more or less common stuff, and I would like to see it integrated in KiCad itself. But I'm not the person who supposed to decide that. Anyway, Brian already busy with doing that in C++, so I believe that's alright. If there will be some dialog with just common geometrical annotation, you still can use python scripts to do some specific one. On Sat, 23 Nov 2019 at 13:30, Dino Ghilardi <dino.ghila...@ieee.org> wrote: > > On 23/11/19 10:05, Alexander Shuklin wrote: > > Hi Dino, > > I would say "back annotation" and "geographical annotation" are just > > different things. We with Brian plan to implement both of them. > > Basically when you want to get references from board and apply them to > > corresponding schematic, that back annotation. If you re-annotate > > footprints in PCB according it's position that's geographical > > annotation. I think we will do geographical annotation, which will > > call back annotation straight away. > > Sometimes there's a reason to have back-annotation without > > geographical annotation: once I was asked by our designer "to rename > > that, that and that one connector", for it would correspond his wires > > numbers and documentation. Of course you can still do it manually, but > > if back annotation will be implemented, why not to let user call it > > alone? > > > > Good point. Having two tools at the price of one would be better than > have one tool only (and having back annotation function exported to > python would open the door to user's personal custom back-annotate scripts). > By the way: How about implementing back annotation in kicad itself and > the "geographical annotation" as a python action-plugin (that calls back > annotation on all selected components)? That would enable users to > create their custom back-annotation scripts with different > "unconventional geometries" easily, just modifying the original script > source. > Drawback: I don't know which of the two methods ("all in c++" or "core > functions in c++ and higher level as a script") will be easier to > implement/debug. > > Cheers, > Dino. > > > > > > > _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp |
_______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
