ID: | 5859 |
From: | rn...@igor2.repo.hu |
Date: | Mon, 24 Oct 2022 06:30:00 +0200 (CEST) |
Subject: | [pcb-rnd] camv-rnd: new: export/print |
Hi all, after the librnd code refactoring ealrier this year, it's much easier to add the standard exporters (png, svg, ps, lpr) to any Ringdove app. I've just done it for camv-rnd. If you are using camv-rnd from source, you get the usual set of export related features with the above generic export plugins: - export menu in the file menu, or {f e} on the keyboard -> export dialog - print menu in the file menu, or {f p} on the keyboard -> print dialog - the usual -x command line option (automated export) Since pcb-rnd cam feature can combine layers freely and you can export the result in the same formats, a valid question is why do we need export feature in camv-rnd at all. Use cases: - if you have to export some gerbers (e.g. for documentation purposes) not generated from pcb-rnd - if you need to combine pcb-rnd exported gerbers/excellons/gcode with similar files coming from non-pcb-rnd sources - since Ringdove is not integrated, camv-rnd is a stand-alone project; there may be users with less capable layout editors lacking cam-like layer composition; a viable workflow there would be to export everything into individual gerber/excellon/gcode files and use a camv-rnd -x command line to combine selected files into whatever format - same premise of weak layout tool, but on export formats: the user would like to embed the drawings in vector form in some document and needs eps or svg but the layout tool can't export that; in fact the only vector format the layout tool can export is gerber; camv-rnd can be used as a simple converter to svg or eps. At the moment all layers are exported and the export matches the screen render, regardless of export flags. This will change some time in the future and we will have the possibility to specify which layers to export and make some other changes to the export. A known bug is: if you draw measure lines, the numbers written on them are not exported. This is because camv-rnd still uses ttf for that. Some time after the librnd4 transition I will switch over camv-rnd to use the (ex-)pcb-rnd font rendering engine, that will solve tis problem. I will probably make Erich's Aussiefont the default for camv-rnd (just like I did in sch-rnd). Best regards, Igor2
Reply subtree:
5859 [pcb-rnd] camv-rnd: new: export/print from rn...@igor2.repo.hu