Mail Archives: geda-user/2012/10/27/18:40:35
Sergey Alyoshin wrote:
> It seems not that much work to
> add title block to schematic, but why should user remove it in each
> new symbol?
I usually start with an existing symbol -- either a similar symbol from
the library or a symbol generated by one of the scripts. So the default
title block never bothered that much. But you are right. The default title
block is not useful for editing symbols. How about including it only if
gschem was called with a *.sym file?
Or an solution that puts the user more in control:
If gschem is called without a preexisting file, issue a dialog that asks
whether you want to work on a new schematic or on a new symbol. In case
of schematic present a list of title blocks to choose from. In case of
symbols, offer a list of symbol templates.
> I don't now how to save symbols without title blocks. Filter them by
> name prefix title? And this would be strange, as user should be
> warned what title block will not be saved. I suppose,
> system-gschemrc.scm should define default-titleblock as "".
At least for me, this would be awkward. If I start gschem with no file,
it will be for a schematic rather than for a symbol.
BTW,there is a diffeence between a titleblock that was loaded on start-up
and one that was introduced later: If the titleblock contains attributes,
these attributes do not get locked. This is relevant for my local titleblock
as shown in gedasymbols
http://www.gedasymbols.org/user/kai_martin_knaak/symbols/titleblock/title-block.sym
That is, you can edit their value and still enjoy a locked titleblock
graphics. If you lock the titleblock later, the attributes also get
locked. You'd have to unlock the titleblock to change their value.
---<)kaiamrtin(>---
--
Kai-Martin Knaak
- Raw text -