Recovery timing errors using clock crossing bridge

In the Assignment Editor, do a Cut Timing assignment from one clock to the other, and then vice-versa.

Actually, I don't mind the clocking being left to the user. It's not to difficult and in reality something I think users need to understand. The one that drives me crazy is development kits without any I/O timing constraints, which users could then use as a template for their own boards, since I/O timing is considerably more complicated.

And yes, it's ignoring the paths(which may change the timing on the next fit, since the fitter can now ignore them too).