| ID: | 3908 |
| From: | Gabriel Paubert <pa...@iram.es> |
| Date: | Fri, 3 Apr 2020 15:11:07 +0200 |
| Subject: | Re: [pcb-rnd] please ACK your bugreports! |
| in-reply-to: | 3901 from ge...@igor2.repo.hu |
| replies: | 3910 from ge...@igor2.repo.hu |
Hi Igor2,
First, congratulations on getting funded to work almost exclusively on
your EDA system.
I've been silent for a few weeks, first adapting to confinement and
because right now I'm mostly writing VHDL code for FPGAs for 3 different
projects, having changed priorities (I was going to assemble a few
prototype boards at work and probably designing a second version of the
PCBs to fix the inevitable bugs on a board with ~500 components).
On Fri, Apr 03, 2020 at 09:20:08AM +0200, gedau@igor2.repo.hu wrote:
> Hi all,
>=20
> after spending some ~10 hours on intensive bugfixing, by now I've manag=
ed=20
> to fix most of the bugs scheduled for this release. Current standing:
>=20
> open=3D3 fixed=3D21 (87.5% waiting for ack); unreproducible=3D1
>=20
> TODO needs ack/clarification from:
>=20
> Barjac: 2
>=20
> Britton: 1
>=20
> Cuvoodoo: 1
>=20
> Gabriel: 4
+ FEATURE: configurable layer keys plus {l l} and {l k} for next and prev=
ious layer ml=3D3411 [report: Gabriel]
FINE: I've not used it much, but it works as expected as far as I can
tell.
+ BUG: changing padstack prototypes from the padstack editor dialog won't=
set the board change flag [report: Gabriel]
FIXED.=20
+ BUG: bug_files/drc/ - redundant drc hits, see README there [report: gpa=
ubert] -> in the new drc at most 2 hits per short are possible: from the =
two directions (two networks), because clearance requirements may be diff=
erent per net
That one is going to take more time, I tried to run drc on my most
recent complex board and I got 23260 violations, taking ~2h20mn in the
process on a core-i7. I'm sure that I have to tune the settings for the
new DRC. So expect a follow up message when I find time.
+ BUG: bug_files/arcedit.lht - grab the lower endpoint for move and it tu=
rns the arc into 360 deg [report: gpaubert]
- mostly fixed for the editing side, although here are still a few
surprises and/or inconsistent behaviour: it's unpredictable whether we
get either 360=B0 or 0=B0 when the mouse is released on the starting
point, but it's a minor issue.
Load the attached example file, move the upper left point of the arc
on top of the lower right: on the left arc, you get a 360=B0 arc, on th=
e
right arc, you get 0=B0. If you move the lower right point on top of th=
e
upper left it's just the opposite. The wireframe shown during editing
correctly indicates what will happen when releasing the mouse button.
What amazes me is that the only difference I have seen (there may be
others that I've missed) between the two arcs is that one has a
starting angle of -90=B0 and the other 270=B0.
- a remaining bug: edit one of the arcs, undo the edit, the enclosing
polygon is not refreshed on undo.
Regards,
Gabriel
Reply subtree:
3908 Re: [pcb-rnd] please ACK your bugreports! from Gabriel Paubert <pa...@iram.es>
3910 Re: [pcb-rnd] please ACK your bugreports! from ge...@igor2.repo.hu
3927 Re: [pcb-rnd] please ACK your bugreports! from Gabriel Paubert <pa...@iram.es>