pcbnew GAL:
The attached screenshot shows some nets that I would've liked to length match as they travel to/from a board to board SMD connector on far right to a chip on the far left. In the middle is a male thru hole header whose purpose is test point access for each of the nets.
The test point pads seem to bisect the nets into two lengths, pre- and post- test pad runs. All the nets are on the top layer, both post- and pre- test pad portions. If one temporarily changes all the test pads to reside only on the back Cu layer, then clicking on any part of the net then shows the full length of the net, extending from SMD connector to chip. The test pads are temporarily set aside. Or so one would think.
When I go to length match these nets, the length detection logic seems to bring the test pads back in and reverts to the bisection. So I am unable to length match the nets, which at this moment, because of the temporary change to my test pads, technically consist of the full run from SMD to chip. The length matching test seems to use different code than the "click on any segment of the net and update the status bar code".
Also, bug #2, during length matching drag, the changing length shown numerically not updating with sufficient granularity, neither for a) mouse movements, and b) nor for numeric meandering wave shaping using the number keys. b) is especially noticeable.
Hi Dick,
Could you send me the board that shows bug #1?
What do you mean by insufficient granularity?
Tom