ID: | 61 |
From: | ge...@igor2.repo.hu |
Date: | Sun, 4 Sep 2016 06:28:49 +0200 (CEST) |
Subject: | Re: [pcb-rnd] pcb issues: grid |
in-reply-to: | 59 from ge...@igor2.repo.hu |
replies: | 62 from Chris Smith <sp...@icloud.com> |
On Sat, 3 Sep 2016, gedau@igor2.repo.hu wrote: Finished the first implemention. Tested them with save-load round trip, looking at preferences/sizes and bottom text (didn't inspect rotue styles). 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? (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) > 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. This should be very similar to mainline git files, except the excess zeros removed. Human readable, no rounding error in round trip. Do we need a 4th, vcs-friendly-mixed-mainline-pcb-rnd variant with the trailing zeros kept? > B. a "compatibility" .pcb, which uses the current %mr, just in case someone > really has a version from between 2010 and 2011 that doesn't handle units > correctly on load. This means no unit suffixes and everything in centimil. Looks like what we had originally, unsuffixed centimils. Round trip results in rounding errors. Pre-2011 mainline should be able to read it. > C. a nanometer unit .pcb; this would use nanometer for all numbers with unit > suffixing. We need this because we lose easy script-processing with A.: your > external scripts would need to understand like 9 different pcb units, and if > the unit list is extended in pcb, all scripts would need to be upgraded > too.... Instead, if you know you are going to feed a script, you could just > use nanometers and lean back. (Note: other users have been complaining on the > ML about mainline and script processing and solution A., so I'm not the only > one worrying about this. In this, we'll be a bit more advanced than mainline, > where you can't choose this runtime, afaik). Script-readable, nm suffixed integer coords, independently of the internal numeric representation/unit. Round trip worked without rounding error. When looking at the file in a text editor, please note: - PolyArea[] has to be written in unsuffixed centimil-square - Thermal[] has to be written in unsuffixed centimils - value 0 is intentionally unsuffixed - looking at your original file, I think mainline keeps grid resolution in centimil with 6 digits, unsuffixed; only our centimil format will do something similar, the rest of the formats will suffix it. Regards, Igor2
Reply subtree:
61 Re: [pcb-rnd] pcb issues: grid from ge...@igor2.repo.hu
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