© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
The patch is not really the best.
It is true that all the burst requester no longer appears, but something does not fit with the net / filter.
If the thickness of the trace remains 0 and you try to change net it happens that the requester of too low thickness ends up under the net list and everything becomes irresponsible because it is waiting for the OK (hidden) for the thickness problem.
Is it not the case that after the notification of a thickness that is too low, the thickness itself is automatically set to the minimum permissible value rather than leaving it at 0?