Feature Suggestion: Board Consistency should be hard to break.

[Anonymous]

I've had several coworkers manage to get their schematics into an inconsistent state.

I suggest that it would make Eagle more user friendly if it were much more difficult to manage this. I think you should explicitly show a dialog asking if they really want to break the connection between the PCB layout and the schematic rather than just showing a warning when they click the board file closed. Obviously it should be possible to do for experts, I'm just seeing this happen in the field repeatedly and I work with older designers who don't notice visual warnings as easily.

[rachaelATWH4]

---

@Anonymous wrote:

I've had several coworkers manage to get their schematics into an inconsistent state.

I suggest that it would make Eagle more user friendly if it were much more difficult to manage this. I think you should explicitly show a dialog asking if they really want to break the connection between the PCB layout and the schematic rather than just showing a warning when they click the board file closed. Obviously it should be possible to do for experts, I'm just seeing this happen in the field repeatedly and I work with older designers who don't notice visual warnings as easily.

---

I'd recommend everybody have the following set:

SET Option.AutoLoadMatchingDrawingFile 1

This way the chances of you having one or the other open and not both is significantly reduced.

But what part of the massive yellow/black stripy banner across the top of the schematics with "F/B annotation is severed" written in it was unclear to your colleagues? How could they not notice this, it's not subtle!

However, I also agree a warning dialog would probably be a good idea so long as there was a way to suppress it for those of us that don't need it.

Best Regards,

Rachael

[Anonymous]

I think it's just a vision acuity thing, to be honest. Plus they use monitors with super high resolution so the bar is nowhere near the area they're looking at.

I definitely notice the bar, but I've had to use ERC/DRC to try to fix a few too many files in the last two months. It should take much more active effort to break the connection. Though to be fair this may be related to dropbox screwing up lock files so badly, I have to disable dropbox syncing to work on my board files without save errors from the lock files being sync'd.

[didrik.madheden]

Perhaps even better: the ability to resolve trivial conflicts directly by adding missing components, much like a non-existent board is created from a schematic initially.