and of course, for the 'online DRC' - it doesnt always have to be MxN, since the operation only has to be on what is changing. Batch DRC, well that is an MxN problem, but can be spun into multi threads if it takes too long. Altium spun the batch DRC (the one you run just before you send it away to be fabbed ) into multi threads a few years ago.
For timing - Altium spent considerable effort making the Xsignals creation completely GUIable- but I do not think it is worth the effort- compared to users defining signal rules and signal groups in text format... (do not forget groups since this info is required so that the signal timing analyser panel wil need to display the group ) *What does need to be in there is that if there is a re-annotation of the design, then if designators are specified in the rule text, the designators need to be updated by the tool to reflect the annotation.* IE if you define signals from U1-15 to U10-3 , now there is an annotation dependency. anyway, you understand. deep inside, altium deals with UUIDS to manage that, bu I dont think that's strictly necessary unless you end up with duplicate designators amongst the timed signal rules ! -- You received this message because you are subscribed to the Google Groups "KiCad Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to devlist+unsubscr...@kicad.org. To view this discussion on the web visit https://groups.google.com/a/kicad.org/d/msgid/devlist/dcc7af84-e1e0-430d-918e-f3870eec55c7n%40kicad.org.
