> this is good for the initial board, but doesn't quite work when you > forward annotate changes to pcb. > > perhaps the forward annotation should be done by writing out a pcb > actions file which has actions to instantiate the new footprints and > load the newly created netlist?
gsch2pcb already reads the pcb file to discover which footprints it doesn't need to duplicate. It could write out new rats at the same time, I suppose, but I don't know how well that would work. If it's already reading a lot about the board, maybe it should just write out a modified board. Time to break the board support files into a library, so we can write nifty tools that know a *lot* about pcb internals? Otherwise, yeah, an action script might be the best way to "import" changes into pcb while it's running.
