Hi Peter,
Thanks for working on and commiting this path code.
[snip]
>Mine is gEDA like too.. it copies the format of text. However, I do like
>the context provided you your suggestion, and it makes hand-editing
>easier. (I never did much like having to manually update a line-count
>when editing text lines).
>
>Note, that the last "1" on the "p ...." line means "one further line of
>path string. You'd want to drop that if you moved to the [...] syntax.
I do like the multi-line syntax better (with an added line count).
Though we have a nice mix of things (text with count, attributes/embedded
symbols with delimiters, and pictures that end with a dot).
Also, I'm not too keen on using a lower-case "p" for the path
identifer. It might confuse people who will think that p and P are
the same. How about something like H (patH)? There are no other lower
case object identifiers.
I'm willing to be convinced in either direction. Also, once
we lock things down, please update the file format documentation on the
wiki and bump the file format version # (in libgeda/defines.h:
#define FILEFORMAT_VERSION 1
).
Also, one minor buglet:
- Printing npn-1.sym to a postscript file, renders the filled arrows in
green (should be black in output-color "disabled" mode).
-Ales
_______________________________________________
geda-dev mailing list
[email protected]
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
