X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h= reply-to:subject:to:references:from:message-id:date:mime-version :in-reply-to:content-type; s=fm2; bh=y3qt7BHgcXKN+9hTPktCv2QNw3Y EjZZ4p+/lHi+it4Y=; b=t/a+6g0umz5F0gSQmw5csqOjBIWN57FQx656Cuo/nKu RnrIz3O1FEd7oszy+TJWC6sbH8+1mg19KVGMnmpl8dhfoxTJmWFW82F7eMb8D74Z 7+BvIsHbcoK2f8aiippcHfmWHNPQwBrS+BqHAF9pxIjIXHyfjZBjsy84hGkCeh6o u19MwxbifPSR0Qufd9lslGJiCW37QhNdpq95YBSIr/odWQscQirXU41OGk1kFo5V WnBciolWbPt11BcgmqV9qU+bZxJwOOaJNt076c3ELevGkjgnIPN3Cw14MDb+ioo3 tYkINFuCNQo+RhfkL4cBfvB71JvD2yd62hgBLexDJnw== X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:reply-to:subject:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=y3qt7BHgcXKN+9hTPktCv2QNw3YEjZZ4p+/lHi+it4Y=; b=WXAxYLwN BrkmMAxD/rHActMLoZxKJGIEDJhEicszHUGBxjbOlqXr9JdclldnfnfxDCpBA2EB uoGP7/JvO57EMDslToNr/o8GPTETonBwISIIDy9XM+l3U1l1hfjzOf6btO0J5x16 SAdpQurQ6Rqe/iCBDeZZ4N5E+L3fB54/aWDkiBxnkZs5PSt88w37EQZmSoZJXQaR JKQBVk+osuJYSOACQWAkyrkuLRslb5jIkcRLJp8nkx0x5huLyhYo8/DXrcYcH93q IBy6AeQike6YubQ1Z4qycSdOuFR4nWIwo1YHl4DGfgsQzVkvgPrQhpknYMmR4XKB 9pYICzs13UCZ7A== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledruddtledgudduiecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthenuceurghilhhouhhtmecu fedttdenucgoufhushhpvggtthffohhmrghinhculdegledmnecujfgurheprhfuvfhfhf fkffgfgggjtgesrgdtreertdefjeenucfhrhhomhepifhirhhvihhnucfjvghrrhcuoehg hhgvrhhrlhesfhgrshhtmhgrihhlrdgtohhmqeenucffohhmrghinhepsghlohhgshhpoh htrdgtohhmpdhgihhthhhusgdrtghomhenucfkphepuddtkedrvdduhedrudelhedrvddt heenucfrrghrrghmpehmrghilhhfrhhomhepghhhvghrrhhlsehfrghsthhmrghilhdrtg homhenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Subject: Re: [geda-user] PCB: Text disappears when converting selection to element. To: geda-user AT delorie DOT com References: From: "Girvin Herr (gherrl AT fastmail DOT com) [via geda-user AT delorie DOT com]" Message-ID: Date: Sat, 16 Feb 2019 10:26:15 -0800 User-Agent: Mozilla/5.0 (X11; Linux i686; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------5C39148E6D9ED7DA5EC6F1B6" Content-Language: en-US Note-from-DJ: This may be spam 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 is a multi-part message in MIME format. --------------5C39148E6D9ED7DA5EC6F1B6 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Erich, Thanks for your reply. I was not aware of the text limitation in pcb. I assumed text was just another silk graphics feature like lines and arcs. Whatever is on the silk layer, stays on the silk layer. It is, after all, just graphics - no intelligence. I guess I could add the text in the pcb design on the silk layer, but that is prone to error. I will check out your utility and see if I can use it. Thanks again. Girvin On 2/15/19 5:15 PM, Erich Heinzle (a1039181 AT gmail DOT com) [via geda-user AT delorie DOT com] wrote: > PCB's data model does not allow arbitrary text in elements much beyond > the refdes. > > To get around this limitation, I wrote the following utility a few > years ago > > http://vk5hse.blogspot.com/2015/09/geda-pcb-footprint-text-utility.html > > https://github.com/erichVK5/FootprintTextForPCB > > Which also supports rendering of a few of the Hershey fonts, too. > > By converting text into a footprint containing line features, these > features can be used by itself or copied and combined with an existing > footprint requiring labels, i.e. C B E for a transistor. > > Without this utility, arbitrary text has to be hand drawn with line > features in gEDA PCB. > > The layout editor pcb-rnd has generalised the data model for > footprints, now known as subcircuits, allowing multiple arbitrary text > features, polygons and arcs. You simply select the features, and > convert them to a subcircuit, which can be cut to buffer and saved as > a standalone "footprint" for later re-use if necessary. pcb-rnd has > also expanded the "terminal" options and internal "no connection" > options for subcircuits for drc connectivity, even allowing pcb spiral > inductors, for example, with electrical terminals at each end that do > not behave like a short. > > Regards, > > Erich > > > On Sat, 16 Feb 2019 10:55 Girvin Herr (gherrl AT fastmail DOT com > ) [via geda-user AT delorie DOT com > ] wrote: > > Greetings, > > I am using pcb 4.1.3 on Slackware Linux. > > I am trying to modify an existing, but renamed, element. I need to > add > text ("+") to the top silk layer. The text gets added and looks to > be on > the top silk layer, but when done and I choose "Convert selection to > element", the text disappears, even though it was selected. I > confirmed > that the resulting element does not have the text on the top silk > layer > when reloaded. However, when I look at the element file (below), I > see > that the text statement is there but assigned to the "copper" > layer 4, > not the "top silk" layer. What am I doing wrong or what is the > trick to > get text on the top silk layer? > > file: > > Element["" "" "C?" "" 200.00mil 200.00mil 790.00mil -30.00mil 0 > 100 ""] > ( >      Pin[-100.00mil 0.0000 65.00mil 30.00mil 71.00mil 35.00mil "" "1" > "edge2"] >      Pin[1700.00mil 0.0000 65.00mil 30.00mil 71.00mil 35.00mil "" "2" > "edge2"] >      ElementLine [700.00mil -50.00mil 900.00mil -50.00mil 10.00mil] >      ElementLine [900.00mil -50.00mil 900.00mil 50.00mil 10.00mil] >      ElementLine [900.00mil 50.00mil 700.00mil 50.00mil 10.00mil] >      ElementLine [700.00mil 50.00mil 700.00mil -50.00mil 10.00mil] >      ElementLine [0.0000 0.0000 700.00mil 0.0000 10.00mil] >      ElementLine [900.00mil 0.0000 1600.00mil 0.0000 10.00mil] > >      ) > Layer(4 "" "copper") > ( >      Text[150.00mil 100.00mil 0 172 "+" "clearline"] > ) > > /file: > > Note that when I load the element and check the groups in > preferences, > there is only a "bottom silk" assigned to group 1 and "top silk" > assigned to group 2. What looks odd is that the "Top side" at the > bottom > is set to Group 1 and the "Bottom side" is set to group 2. Just the > opposite. Is this correct? > > Is there a good document for the element file statement definitions? > Mine is so old it does not list the "Layer" or "Text" statements. > > Thanks. > Girvin Herr > > --------------5C39148E6D9ED7DA5EC6F1B6 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

Erich,

Thanks for your reply.

I was not aware of the text limitation in pcb. I assumed text was just another silk graphics feature like lines and arcs. Whatever is on the silk layer, stays on the silk layer. It is, after all, just graphics - no intelligence. I guess I could add the text in the pcb design on the silk layer, but that is prone to error. I will check out your utility and see if I can use it.

Thanks again.

Girvin


On 2/15/19 5:15 PM, Erich Heinzle (a1039181 AT gmail DOT com) [via geda-user AT delorie DOT com] wrote:
PCB's data model does not allow arbitrary text in elements much beyond the refdes.

To get around this limitation, I wrote the following utility a few years ago



Which also supports rendering of a few of the Hershey fonts, too.

By converting text into a footprint containing line features, these features can be used by itself or copied and combined with an existing footprint requiring labels, i.e. C B E for a transistor.

Without this utility, arbitrary text has to be hand drawn with line features in gEDA PCB.

The layout editor pcb-rnd has generalised the data model for footprints, now known as subcircuits, allowing multiple arbitrary text features, polygons and arcs. You simply select the features, and convert them to a subcircuit, which can be cut to buffer and saved as a standalone "footprint" for later re-use if necessary. pcb-rnd has also expanded the "terminal" options and internal "no connection" options for subcircuits for drc connectivity, even allowing pcb spiral inductors, for example, with electrical terminals at each end that do not behave like a short.

Regards,

Erich


On Sat, 16 Feb 2019 10:55 Girvin Herr (gherrl AT fastmail DOT com) [via geda-user AT delorie DOT com] <geda-user AT delorie DOT com wrote:
Greetings,

I am using pcb 4.1.3 on Slackware Linux.

I am trying to modify an existing, but renamed, element. I need to add
text ("+") to the top silk layer. The text gets added and looks to be on
the top silk layer, but when done and I choose "Convert selection to
element", the text disappears, even though it was selected. I confirmed
that the resulting element does not have the text on the top silk layer
when reloaded. However, when I look at the element file (below), I see
that the text statement is there but assigned to the "copper" layer 4,
not the "top silk" layer. What am I doing wrong or what is the trick to
get text on the top silk layer?

file:

Element["" "" "C?" "" 200.00mil 200.00mil 790.00mil -30.00mil 0 100 ""]
(
     Pin[-100.00mil 0.0000 65.00mil 30.00mil 71.00mil 35.00mil "" "1"
"edge2"]
     Pin[1700.00mil 0.0000 65.00mil 30.00mil 71.00mil 35.00mil "" "2"
"edge2"]
     ElementLine [700.00mil -50.00mil 900.00mil -50.00mil 10.00mil]
     ElementLine [900.00mil -50.00mil 900.00mil 50.00mil 10.00mil]
     ElementLine [900.00mil 50.00mil 700.00mil 50.00mil 10.00mil]
     ElementLine [700.00mil 50.00mil 700.00mil -50.00mil 10.00mil]
     ElementLine [0.0000 0.0000 700.00mil 0.0000 10.00mil]
     ElementLine [900.00mil 0.0000 1600.00mil 0.0000 10.00mil]

     )
Layer(4 "" "copper")
(
     Text[150.00mil 100.00mil 0 172 "+" "clearline"]
)

/file:

Note that when I load the element and check the groups in preferences,
there is only a "bottom silk" assigned to group 1 and "top silk"
assigned to group 2. What looks odd is that the "Top side" at the bottom
is set to Group 1 and the "Bottom side" is set to group 2. Just the
opposite. Is this correct?

Is there a good document for the element file statement definitions?
Mine is so old it does not list the "Layer" or "Text" statements.

Thanks.
Girvin Herr


--------------5C39148E6D9ED7DA5EC6F1B6--