| ID: | 5644 |
| From: | rn...@igor2.repo.hu |
| Date: | Fri, 13 May 2022 13:40:02 +0200 (CEST) |
| Subject: | Re: printer calibration (Re: [pcb-rnd] poll RESULT: print dialog |
| in-reply-to: | 5643 from ka...@aspodata.se |
On Fri, 13 May 2022, karl@aspodata.se wrote: >Igor2: >... >> Conclusions #1: >> >> 2. when last calibrated > >This thing about calibration was up in this mailing list a year ago, >in the thread with subject "feature removal RFC: the pscalib action" Yes and no: it's the same calibration, but a different aspect/level. Back then it was a specific action (pscalib), which then got removed. That action was supposed to help the user doing the calibration by generating test images, reading back measurements, calculating calibration values. But it was not really working and my impression was that nobody really missed it. That thread was about only that one action, not about ps or lpr calibration argument. The thread resulted in removal of that action, and the whole ps/lpr code got a bit simpler. It was already a preparation for moving these exporters (ps and lpr, among with eps, svg and png) out from pcb-rnd to librnd, but back then I didn't yet see when exactly it could happen. It's rather complicated when you want to keep API compatibility for certain time. The current poll was about the low level calibration export option in lpr and ps, which I didn't remove back then. I thought they would be in the way of moving the code out to librnd, but I've found a way to keep them pcb-rnd only, and the code size is acceptable, API complication acceptabne, so I am going to keep it for now. At least for pcb-rnd, because I won't add these options in other ringdove apps. Best regards, Igor2
Reply subtree:
5644 Re: printer calibration (Re: [pcb-rnd] poll RESULT: print dialog from rn...@igor2.repo.hu