Quite - that's exactly my point about possibilities of optimisation - lots of options for how to do so. But all those require re-architecting of existing underlying 'stuff' to enable it. (Batch DRC already uses worker threads, by the way, for some types of rules, but not currently for the length / skew constraints as they are relatively quick to run, but haven't yet explored them in the interactive context.
For signals, the integration with the DRC is actually going to fairly simple, the smart moves will be in how to integrate them in the schematic capture. I don't think text interface as the primary route for signals makes sense. Whether it ends up as wizard-driven as Altium I couldn't say. Haven't really put a huge amount of thought in to it yet. But some simple way of defining signals will be pretty key. James. On Fri, 1 Mar 2024 at 22:17, Glen English <glenenglish1...@gmail.com> wrote: > 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/CAMVX%3DtYtGAhSwpW%2BTAXa2KJ%2B0OY4C%2B9dbA5Sewu2oN2TMS%3DLLw%40mail.gmail.com.
