Mail Archives: geda-user/2016/03/31/08:02:54
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
--8323329-1016304109-1459425591=:1677
Content-Type: TEXT/PLAIN; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8BIT
On Thu, 31 Mar 2016, Chris Smith (space DOT dandy AT icloud DOT com) [via
geda-user AT delorie DOT com] wrote:
> In gschem (1.9.1) I add a component from the library and choose ‘embed
> component’ rather than ‘reference component’. My expectation is that if
> I use ‘down symbol’, edit the symbol then use ‘up’ it would update the
> embedded component in my schematic, however this doesn’t work: it asks
> me to save the symbol then complains because it is trying to overwrite
> the original symbol file, to which I have no user write permission.
>
> Is this supposed to work? Is there a setting that controls it?
As far as I know, this isn't implemented in gschem.
I'd recommend having a local copy of the symbol you want to embed (I
usually have a subdirectory "lib" for that), editing this file as usual
using "down symbol", and optionally embedding it as a last step before
sharing the schematic. It might even be preferable to not embed the
symbols at all and share a tarball (or git repository) with the schematic
and the symbols as individual files.
If you already embedded the symbol and don't have a copy of the original
symbol file, you could use "xorn extract schematic.sch symbol.sym" to
extract the embedded symbol from the schematic.
--8323329-1016304109-1459425591=:1677--
- Raw text -