X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Date: Fri, 9 Feb 2018 14:37:15 +0100 (CET) X-X-Sender: igor2 AT igor2priv To: "Richard Rasker (rasker AT linetec DOT nl) [via geda-user AT delorie DOT com]" X-Debug: to=geda-user AT delorie DOT com from="gedau AT igor2 DOT repo DOT hu" From: gedau AT igor2 DOT repo DOT hu Subject: Re: [geda-user] Another PCB grid step question In-Reply-To: Message-ID: References: <6221de93-bb98-d397-79b4-eecf3975c2e6 AT linetec DOT nl> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1906609639-1518183435=:12270" Reply-To: geda-user AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-user AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-1906609639-1518183435=:12270 Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Hello Richard, On Fri, 9 Feb 2018, Richard Rasker (rasker AT linetec DOT nl) [via geda-user AT delor= ie.com] wrote: > OK, I did some checking, and I now see that I overlooked the 'File format= '=20 > option when saving the design. The default 'lihata' format is not=20 > PCB-compatible. > > Still a bit strange though, as I started out with a geda/pcb file. But I= =20 > probably wasn't paying attention when saving it (and the first time I use= d=20 > pcb-rnd, it was still from /trunk/src, without actually installing it -- = maybe=20 > this had something to do with it). Cool, thanks! Just wanted to make sure I didn't miss a bug. For those who haven't tried pcb-rnd yet: all these complications with the= =20 file formats are neeed because we load mainline's files, 2 dialects of=20 kicad files, 2 dialects of eagle files, hyperynx files, protel/autotrax=20 files, tEDAx files and we can save to most of these formats as well.=20 (Thanks to Erich for the countless hours of reverse engineering and=20 testing!) The file format policy is roughly this: 1. if you load a file, pcb-rnd will automatically determine the format=20 (unless you explicitly asked for a specific format - that's possible only= =20 via the CLI/action interface); this is remembered as the 'original' file=20 format 2. if you just 'save', it should save in the same original format you=20 loaded from (or last saved in) 3. if you do a 'save as', you can select the format; by default, it should= =20 offer the same format as it would save under pont 2. 4. if you do anything that involves creating a new board, then the new=20 board is not "loaded", so it doesn't have such an "original format". When= =20 you save, or save as, it will default to our native format, lihata. If you experience any deviation from this, please let me know, because=20 that means you found a bug! (A common way to trigger 4 is: start a new layout, import something=20 through the buffer or from the import menu; neither the buffer nor the=20 import menu would "infect" your new board with a different format.) Just for the record: in-memory, there's no file format. In other words,=20 the in-memory representation is yet another format, different from any=20 disk file format. So any load from or save to any file format is really a= =20 conversion. (This is the same in PCB and basically in any software that=20 doesn't save a memory dump but uses an exporter and a parser.) > (There's a LOT of new stuff in pcb-rnd, and I haven't had time yet to exp= lore=20 > it all -- but knowing about the file formats saves me some head-scratchin= g=20 > :-)=C2=A0 ) Thanks for exploring! Best regards, Igor2 --0-1906609639-1518183435=:12270--