| ID: | 3927 |
| From: | Gabriel Paubert <pa...@iram.es> |
| Date: | Sun, 5 Apr 2020 18:43:46 +0200 |
| Subject: | Re: [pcb-rnd] please ACK your bugreports! |
| in-reply-to: | 3910 from ge...@igor2.repo.hu |
On Sat, Apr 04, 2020 at 05:26:54AM +0200, gedau@igor2.repo.hu wrote: > Hello Gabriel, >=20 > On Fri, 3 Apr 2020, Gabriel Paubert wrote: >=20 > > Hi Igor2, > > > >First, congratulations on getting funded to work almost exclusively on > >your EDA system. >=20 > Thanks! >=20 > >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 differe= nt > >projects, having changed priorities (I was going to assemble a few > >prototype boards at work and probably designing a second version of th= e > >PCBs to fix the inevitable bugs on a board with ~500 components). >=20 > 500 component boards, wow, no wonder you need all the optimizations in = the=20 > code! Well, when you do RF boards, the number of passives, especially capacitors, is always large. Many chips need 20--30 passives for supply decoupling and filtering. Even a fairly simple differential amplifier (LMH3401) needs over 10 passive around it, and I have 8 on this design for single-ended to differential conversion in a DC-2GHz+ band. On that board there are 218 capacitors, 95 resistive components (some are RF attenuators, so not only dipoles) and 57 inductive components (standard chokes, common mode filters, ferrite beads and EMI filters). That's already 350+ components. [snip] > > > >+ BUG: bug_files/arcedit.lht - grab the lower endpoint for move and it= turns 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= the > > right arc, you get 0=B0. If you move the lower right point on top of= the > > upper left it's just the opposite. The wireframe shown during editin= g > > correctly indicates what will happen when releasing the mouse butto= n. > > > > > > 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. >=20 > Thanks, this is something I also found, but after looking around in the= =20 > code a bit I accepted that behaviour: >=20 > - when the two endpoints are the same coord, both 0 and 360 delta value= s=20 > are valid solutions >=20 > - both the 0 and the 360 are special cases; it is very easy to mess the= m=20 > up when using the GUI, e.g. getting 1 instead of 0 or 358 instead of=20 > 360, because of grid settings and inaccurate placement. As an user, I'd= =20 > always use the property editor if I wanted to make sure I have 0 or 360= =20 > deg. >=20 > So I think this is not a bug (not a feature either, just how it is) and= =20 > take the bug resolved. >=20 Ok, no problem. > >- a remaining bug: edit one of the arcs, undo the edit, the enclosing > > polygon is not refreshed on undo. >=20 >=20 > Thanks, this is a new bug. Added to the TODO, will be handled soon. >=20 Fixed indeed, thanks. Regards, Gabriel
Reply subtree:
3927 Re: [pcb-rnd] please ACK your bugreports! from Gabriel Paubert <pa...@iram.es>