Eagle importer problems and stable net names

[Reece R. Pollack]

Hi folks,

I'd like to get some comments on the possible solutions to a problem in the Eagle importer I documented in Issue 14620.

In brief, the Eagle importer drops all of the intra-sheet network names when importing t schematic, but retains those net names when importing the board. This breaks cross-probing for all but inter-sheet nets. I've proposed three possible solutions, and identify one which I think is the best.

The reason this issue is of particular interest to me is that some years ago I started a project using Eagle consisting of 5 related boards. The schematics are complete, and one of the boards has been fabbed and tested. The others are in various stages of layout, and I was hoping to complete them using KiCad rather than going back to Eagle. However, the loss of the net names in the imported schematics, and the resulting inability to cross-probe nets, is blocking.

Seth pointed out that there is also a pending request to maintain unlabeled net names in KiCad with schematic and software changes. Has there been any significant thought given to how this request could be addressed?  Before I think about digging into the workings of the Eagle importer, I'd like to know more about this. Perhaps the proper way to solve my issue is one that could also satisfy this request?

-Reece