| ID: | 62 |
| From: | Chris Smith <sp...@icloud.com> |
| Date: | Sun, 04 Sep 2016 10:16:20 +0100 |
| Subject: | Re: [pcb-rnd] pcb issues: grid |
| in-reply-to: | 61 from ge...@igor2.repo.hu |
| replies: | 64 from ge...@igor2.repo.hu |
Hi Igor2, > On 4 Sep 2016, at 05:28, gedau@igor2.repo.hu wrote: >=20 > Finished the first implemention. Tested them with save-load round = trip, looking at preferences/sizes and bottom text (didn't inspect rotue = styles). >=20 > Chris, please test it on your system to see if round trips are the = same as mines. If you have mainline from git in a Linux virtual box, = could you please try whether it loads all 3 formats properly? >=20 > (Note the new format combo box in the Save As dialog box. Default is = the old centimil for now, until we can confirm the human readable format = doesn't break) Mainline git reads all three formats properly. Interestingly, mainline saves units as =E2=80=98mm=E2=80=99 with four = digits of precision. I don=E2=80=99t know where the nanometer = resolution fits in to this. >> A. a natural unit .pcb; this would be the default .pcb long term. It = would save using %06$mS; as far as I can tell, this would work with any = mainline starting at least from 2011. This uses unit suffixes and = "random" units. >=20 > This should be very similar to mainline git files, except the excess = zeros removed. Human readable, no rounding error in round trip. I honestly don=E2=80=99t know where you=E2=80=99re going with this one. = I have several lines in a .pcb which have mixed units, i.e. offsets in = nm and thickness in mils. IMHO, that=E2=80=99s not readable, it=E2=80=99s= just confusing. I=E2=80=99m of the opinion that the =E2=80=98natural=E2=80=99 units = should be whatever the drawing units are for the .pcb, with enough = precision to represent nanometers. If I use footprints in other units = (mils) then I understand that these are =E2=80=98foreign=E2=80=99 units = and will be converted to the natural units on import. What matters to = me is consistency =E2=80=94 I don=E2=80=99t mind so much about rounding = errors when converting foreign units, rather that the result is exactly = the same over save/reload cycles. > Do we need a 4th, vcs-friendly-mixed-mainline-pcb-rnd variant with the = trailing zeros kept? IMHO, no. People should probably accept that if they=E2=80=99re using = different software, the file may be slightly different on save. > When looking at the file in a text editor, please note: >=20 > - PolyArea[] has to be written in unsuffixed centimil-square >=20 > - Thermal[] has to be written in unsuffixed centimils >=20 > - value 0 is intentionally unsuffixed Why is this, out of interest? Regards, Chris =E2=80=94 Chris Smith <space.dandy@icloud.com>
Reply subtree:
62 Re: [pcb-rnd] pcb issues: grid from Chris Smith <sp...@icloud.com>
64 Re: [pcb-rnd] pcb issues: grid from ge...@igor2.repo.hu