Re: gEDA-user: crosshair snaps to pins and pads... on locked component
Felipe De la Puente Christen wrote: > May be it's better to have "Position Lock" *and* "Ignore Element" as > different actions. +1 locked position and ignored element should be independent attributes. The current snapping politics ignores lines on silk. This can be annoying, too. For example, mechanical hints in footprints are necessarily in silk. It would facilitate alignment if the cursor would snap to these lines. ---<)kaimartin(>--- -- Kai-Martin Knaak Öffentlicher PGP-Schlüssel: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x6C0B9F53 ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
gEDA-user: (hierarchy-uref-mangle "disabled") doesn't seem to work when generting a bom
Hello group I am doing my first hierarchial design. In my local gnetlistrc I have (hierarchy-uref-mangle "disabled") un-commented as I don't want the Sn_ in the front of the uref. gsch2pcb does what I desire and correctly drops the "Sn_" prefix. When generating a bom. The prefix is not dropped which is NOT what I want. If I change from (hierarchy-uref-order "append") to (hierarchy-uref-order "prepend") The Sn_ value is placed at the end, so gnetlistrc seem to be picked up, but I'm not sure where as I don't see it in the .scm that I'm using. My command line syntax is gnetlist -g xmlbom circuit.sch -o circuit-bom.xml I tried the nomunge option, but it didn't seem to have any effect. gnetlist --nomunge -g xmlbom circuit.sch -o circuit-bom.xml Yes, I am using a scheme that I hacked from gnet-bom(2?).scm (see attached). So I'm probably at fault, but I don't know where. Could anyone give me some pointers as to what I'm doing wrong? Thanks in advance Mike ;;; gEDA - GPL Electronic Design Automation ;;; gnetlist - gEDA Netlist ;;; Copyright (C) 1998-2007 Ales Hvezda ;;; Copyright (C) 1998-2007 gEDA Contributors (see ChangeLog for details) ;;; ;;; This program is free software; you can redistribute it and/or modify ;;; it under the terms of the GNU General Public License as published by ;;; the Free Software Foundation; either version 2 of the License, or ;;; (at your option) any later version. ;;; ;;; This program is distributed in the hope that it will be useful, ;;; but WITHOUT ANY WARRANTY; without even the implied warranty of ;;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the ;;; GNU General Public License for more details. ;;; ;;; You should have received a copy of the GNU General Public License ;;; along with this program; if not, write to the Free Software ;;; Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. ;; -- ;; ;; Bill of Material backend written by Matt Ettus starts here ;; ;;; Bill Of Materials Generator ;;; You must have a file called attribs in the pwd ;;; The file should be a text list of attributes you want listed, ;;; One per line. No comments are allowed in the file. ;;; Questions? Contact m...@ettus.com ;;; This software is released under the terms of the GNU GPL ;; Xml Bill of Materials backend written by Mike Crowe starts here ;; shamelessly changed to format output as an xml document ;; question on xml changes should go to mcr...@gcdataconcepts.com ;; converts a bill of materials to a simple bom where the QNames are the ;; schematic attribute names and the geda values are xml CText ;; from here one should be able to .xsl to parse the xml bom ;; to ones own needs. (use-modules (ice-9 rdelim)) ;; guile-1.8 fix (define xmlbom (lambda (output-filename) (let ((port (if (string=? "-" output-filename) (current-output-port) (open-output-file output-filename))) (attriblist (xmlbomparseconfig (open-input-file "attribs" ; (xmlbomprintlist (cons 'refdes attriblist) port #\:) ; (newline port) (display "\n" port) (display "\n" port) (display "\n\t" port) (xmlbomprintbom port (xmlbomcomponents packages attriblist) attriblist) (display "\n\n" port) (close-output-port port) ) ) ) (define xmlbomprintbom (lambda (port bomlist attriblist) (if (not (null? bomlist)) (if (not (null? (caar bomlist))) ; here if a reference designator (begin (display (caaar bomlist) port) (if (not (null? (cdaar bomlist))) (write-char #\, port) ) (xmlbomprintbom port (cons (cons (cdaar bomlist)(cdar bomlist))(cdr bomlist)) attriblist) ) ; else if anything else (begin (display "\n" port) (xmlbomprintlist (cdar bomlist) port #\: attriblist) ( if (not (null? (cdr bomlist))) (display "\n\n\t" port) ) (xmlbomprintbom port (cdr bomlist) attriblist) ) ) ) ) ) (define (string-insert s i t) (string-replace s t i i)) (define (xmlsearchandappend s1 sstring rstring spos) (let ((fpos1 (string-contains s1 sstring spos))) (if fpos1 (xmlsearchandappend (string-insert s1 (+ 1 fpos1) rstring) sstring rstring (+ fpos1 (string-length rstring))) s1))) (define xmlbomprintlist (lambda (ls port delimiter attriblist) (if (null? ls) #f (begin (display "\t<" port) (display (car attriblist) port) (display ">" port) (display (xmlsearchandappend (car ls) "&" "amp;" 0) port) ; (display (car ls) port) (display "\t\n" port) (if (null? (cdr ls)) (display "" port) ) (xmlbomprintlist (cdr ls) port delimiter (cdr attriblist))) ) ) ) ; Parses attrib file. Returns a list of read attributes. (define xmlbomparseconfig (lambda (port) (let ((read-from-file (read-delimited " \n\t" port))) (cond ((eof-object? read-from-file) '()) ((= 0 (string-length re
Re: gEDA-user: crosshair snaps to pins and pads... on locked component
On Thu, 2 Sep 2010 16:03:55 -0400 DJ Delorie wrote: > What a coincidence. We were just discussing that on IRC. > > I think snap-to-locked is OK, but I want locked *elements* to be > ignored. I have one design that has a big LCD covering up all my > other parts, it's really hard to edit when every operation tags the > LCD instead of the parts under it. What a coincidence. I am editing a board right now with a big LCD covering it all! :-) Levente -- Levente Kovacs http://levente.logonex.eu ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: crosshair snaps to pins and pads... on locked component
I just can't figure out why can't the "Crosshair snaps to pins/pads" work when the component is locked. As far as I know, locking a component is for to lock the position of the component. What a coincidence. We were just discussing that on IRC. I think snap-to-locked is OK, but I want locked *elements* to be ignored. I have one design that has a big LCD covering up all my other parts, it's really hard to edit when every operation tags the LCD instead of the parts under it. How about snapping to pads on the far side? That can get pretty annoying for me. I want to see pads on the other side so I know where I can place vias, but I don't want to snap to them. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: crosshair snaps to pins and pads... on locked component
On Thu, 2010-09-02 at 16:03 -0400, DJ Delorie wrote: > > I just can't figure out why can't the "Crosshair snaps to pins/pads" work > > when > > the component is locked. As far as I know, locking a component is for to > > lock > > the position of the component. > > What a coincidence. We were just discussing that on IRC. > > I think snap-to-locked is OK, but I want locked *elements* to be > ignored. I have one design that has a big LCD covering up all my > other parts, it's really hard to edit when every operation tags the > LCD instead of the parts under it. May be it's better to have "Position Lock" *and* "Ignore Element" as different actions. I have passed trough both situations, and would be great to be able to use them independently. Best Regards, Felipe. -- Felipe De la Puente Christen Mobile Phone: +56 9 93199807 MSN/GTalk : fdelapue...@gmail.com ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: crosshair snaps to pins and pads... on locked component
> I just can't figure out why can't the "Crosshair snaps to pins/pads" work when > the component is locked. As far as I know, locking a component is for to lock > the position of the component. What a coincidence. We were just discussing that on IRC. I think snap-to-locked is OK, but I want locked *elements* to be ignored. I have one design that has a big LCD covering up all my other parts, it's really hard to edit when every operation tags the LCD instead of the parts under it. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
gEDA-user: crosshair snaps to pins and pads... on locked component
Hi folks, I just can't figure out why can't the "Crosshair snaps to pins/pads" work when the component is locked. As far as I know, locking a component is for to lock the position of the component. I think it would be nice when anything could be done with a locked component except accident move. Anyone? -- Levente Kovacs http://levente.logonex.eu ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: gschem doesn't store slot info?
On Sep 2, 2010, at 10:29 AM, DJ Delorie wrote: > I used the Edit->Slot option in gschem to change the slot of a dual > opamp, and it didn't take. Schematic showed the right pins, gnetlist > said otherwise. Saved schematic, surprisingly, had no reference to > the slot. Turns out, even save/revert throws the slot info away! > Manually adding a "slot" attribute works. I believe putting "slot" in your always-promote-attributes list in gafrc also fixes this if the symbol file includes a default slot, which it should. John Doty Noqsi Aerospace, Ltd. http://www.noqsi.com/ j...@noqsi.com ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: gschem doesn't store slot info?
On Sep 2, 2010, at 10:38 AM, John Doty wrote: > Sounds like bug 2949232, listed as "Closed" on the Sourceforge tracker. That > was in 1.6.0. I don't know if the fix propagated to 1.6.1, or whether you > need the git source for the fix. On Sep 2, 2010, at 10:42 AM, DJ Delorie wrote: > > Well, I did a git fetch/rebase, built, and installed... and still > there. "About" says 20100214, gitk says no commits since May, do I > have the wrong repository? The gschem binary is dated today. Is Peter C. in the house? John Doty Noqsi Aerospace, Ltd. http://www.noqsi.com/ j...@noqsi.com ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: gschem doesn't store slot info?
Well, I did a git fetch/rebase, built, and installed... and still there. "About" says 20100214, gitk says no commits since May, do I have the wrong repository? The gschem binary is dated today. [core] repositoryformatversion = 0 filemode = true bare = false logallrefupdates = true [remote "origin"] url = git://git.gpleda.org/gaf fetch = +refs/heads/*:refs/remotes/origin/* [branch "master"] remote = origin merge = refs/heads/master ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: gschem doesn't store slot info?
Sounds like bug 2949232, listed as "Closed" on the Sourceforge tracker. That was in 1.6.0. I don't know if the fix propagated to 1.6.1, or whether you need the git source for the fix. On Sep 2, 2010, at 10:29 AM, DJ Delorie wrote: > I used the Edit->Slot option in gschem to change the slot of a dual > opamp, and it didn't take. Schematic showed the right pins, gnetlist > said otherwise. Saved schematic, surprisingly, had no reference to > the slot. Turns out, even save/revert throws the slot info away! > Manually adding a "slot" attribute works. John Doty Noqsi Aerospace, Ltd. http://www.noqsi.com/ j...@noqsi.com ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
gEDA-user: gschem doesn't store slot info?
I used the Edit->Slot option in gschem to change the slot of a dual
opamp, and it didn't take. Schematic showed the right pins, gnetlist
said otherwise. Saved schematic, surprisingly, had no reference to
the slot. Turns out, even save/revert throws the slot info away!
Manually adding a "slot" attribute works.
$ gnetlist -g PCB slot-1.sch
unnamed_net2R1-2 U1-1
unnamed_net1R1-1 U1-1
v 20091004 2
C 43300 50900 1 0 0 dual-opamp-1.sym
{
T 43500 53200 5 10 0 0 0 0 1
device=DUAL_OPAMP
T 43500 51800 5 10 1 1 0 0 1
refdes=U1
T 43500 52800 5 10 0 0 0 0 1
footprint=SO8
T 43500 53400 5 10 0 0 0 0 1
symversion=0.2
}
C 43100 49000 1 0 0 dual-opamp-1.sym
{
T 43300 51300 5 10 0 0 0 0 1
device=DUAL_OPAMP
T 43300 49900 5 10 1 1 0 0 1
refdes=U1
T 43300 50900 5 10 0 0 0 0 1
footprint=SO8
T 43300 51500 5 10 0 0 0 0 1
symversion=0.2
}
C 45000 50100 1 0 0 resistor-1.sym
{
T 45300 50500 5 10 0 0 0 0 1
device=RESISTOR
T 45200 50400 5 10 1 1 0 0 1
refdes=R1
T 45000 50100 5 10 0 0 0 0 1
footprint=0603
}
N 44300 51300 45000 51300 4
N 45000 51300 45000 50200 4
N 44100 49400 45900 49400 4
N 45900 49400 45900 50200 4
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
