X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Injected-Via-Gmane: http://gmane.org/
To: geda-user AT delorie DOT com
From: Kai-Martin Knaak <kmk AT familieknaak DOT de>
Subject: Re: [geda-user] import SVG into PCB
Date: Thu, 08 May 2014 00:04:41 +0200
Lines: 33
Message-ID: <lkealq$bie$1@ger.gmane.org>
References: <CAHBVutAFneurHxe2Tbsjx0mybFzUL=wuB8GaNyd5mXPu-pvWsA AT mail DOT gmail DOT com> <201405061601 DOT s46G1YMc019081 AT envy DOT delorie DOT com> <CANqhZFzOzk+WOW5_-szpW5p80HDERtooP005FpAtX5D21Dn42Q AT mail DOT gmail DOT com> <CALT8Ef7CUD3UGkNQ5-W0jafyGPzXwKd==2nEMsKZjy_CXHUtcw AT mail DOT gmail DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7Bit
X-Complaints-To: usenet AT ger DOT gmane DOT org
X-Gmane-NNTP-Posting-Host: a89-182-140-216.net-htp.de
User-Agent: KNode/4.11.5
Reply-To: geda-user AT delorie DOT com

Shashank Chintalagiri wrote:

> However, the layer on which the silk
> graphics show up is not always silk. If the number of layers
> changes, then the elements I want on silk show up elsewhere. Is
> there a way to fix this? Footprints know how to put features on silk
> irrespective of layer count and ordering. 

This works because footprint files can only have three layers: top, 
bottom and silk. The third layer in a footprint file is always silk.


> Can the mechanism used there be used here as well?

This is my workaround: 
I made my logo a regular footprint
      buffer->convert_to_element->save_to_file
I also added a logo symbol to my gschem library. So I add the logo.sym 
in the schematic and pcb automatically loads the logo into the layout 
like any other footprint.

The real fix would be a complete rewrite of the internal layer 
representation of pcb. The current model poses major obstacles to some 
highly desirable improvements. E.g. blind and buried vias, the ability 
to copy-paste between layouts with different layer stacks, a comment 
layer that is ignored for all DRC, etc. Of course, this would also 
mean modifications to the file format. If I remember correctly, it was 
consensus among developers that such rewrite should be done. However, 
nobody stepped forward to actually design and implement an improved 
concept. If anyone likes to pick up this project, I'd be willing to 
help with whatever I can. 

---<)kaimartin(>---