Lorenzo Marcantonio wrote:
Only another playground... its the bounding tile of the component,
Hmm, but if you use it mainly for rework, adjacent components could
share the courtyard, no ? After all, you'll inspect or (de)solder
them one by one, not simultaneously.
Also, what do you do with
Dick Hollenbeck wrote:
[...] Installed (e.g. value=DNS) [...]
What would you think of elevating Installed (or whatever it
would be called in the end) to the rank of Footprint ? I.e., a
permanent field with an immutable name.
That way, eeschema could automaticaly flag absent components,
e.g., by
On 6/14/2010 5:39 AM, Werner Almesberger wrote:
Let me see if I got all the bits in your description:
default field names:
- are hard-coded (or equivalent) into KiCad,
- can be overridden by wanted or user-defined field names.
wanted aka template field names:
- are assigned by a global
On 06/14/2010 12:05 PM, Werner Almesberger wrote:
Dick Hollenbeck wrote:
You have good reading comprehension.
Heh, thanks :-)
template aka wanted, not wanted aka template. The distinction
is important since I have started coding it, and the source reflects the
latter term.
Hi All,
Dick, your improvement makes a lot of sense. I think I'm right in
thinking that what my patch would do in the case of importing a 3rd
party library would be to import the field names from that library,
without adding the template field names . Being able to add the
template field names on
[ Belatedly changed the subject, to look better in that thread
hijacking trial. ]
Thanks for your description. Now I understand better where those
heavy symbols come from. Okay, not crazy. Not at all. But still
flawed ;-)
I agree that CPNs make things a lot easier, but managing them also
has a
6 matches
Mail list logo
