Re: gEDA-user: Feature requests printout and export

2008-11-22 Thread DJ Delorie
> * default postscript output name is "foo.ps". With multi page output > this results in strange filenames like > "foo.ps.frontassembly.ps".Feature request: multipage should output > file names like foo.frontassembly.ps by default. Fixed. ___ g

Re: gEDA-user: Surface mount LEDs

2008-11-22 Thread DJ Delorie
> While I'm mentioning it... I'll gamble that DJ is actually reading > this and make an enhancement request: It would be nice if the > generated footprint aways included comments with my original input > in the generated symbol, so I could remember how I get > there... something like the comments

Re: gEDA-user: Just another minor pcb bug

2008-11-22 Thread DJ Delorie
> If Auto enforce DRC clearance is on, lines (traces) starting from a > pad always snap to one of the pad endpoints. This appears to be completely intentional, although I don't know the reason behind it. if (TEST_FLAG (AUTODRCFLAG, PCB) && Settings.Mode == LINE_MODE) {

Re: gEDA-user: Just another minor pcb bug

2008-11-22 Thread Stefan Salewski
Am Samstag, den 22.11.2008, 16:19 -0800 schrieb Ben Jackson: > On Sun, Nov 23, 2008 at 12:33:33AM +0100, Stefan Salewski wrote: > > > > SHIFT makes no difference for this bug -- "Crosshair snaps to pins and > > pads" is off, "Auto enforce DRC clearance" is on. Snaps to pad > > endpoints. If I swit

Re: gEDA-user: Just another minor pcb bug

2008-11-22 Thread Ben Jackson
On Sun, Nov 23, 2008 at 12:33:33AM +0100, Stefan Salewski wrote: > > SHIFT makes no difference for this bug -- "Crosshair snaps to pins and > pads" is off, "Auto enforce DRC clearance" is on. Snaps to pad > endpoints. If I switch "Auto enforce DRC clearance" off snap to grid > points works fine as

Re: gEDA-user: (no subject)

2008-11-22 Thread Martin Maney
> * Spice netlister for gnetlist > R5 1 +9V 1M > V1 n0 0 AC > R4 0 4 100K > R3 0 3 470 > Q1 1 3 2 2N5245 > R2 2 +9V 1K > R1 0 1 1M > C3 2 4 4.7uf > C2 3 0 .052uf > C1 n0 1 4.7uf > .END I don't see a DC source connected to the "+9V" node. -- Unlike some other template languages, you can not arbi

Re: gEDA-user: (no subject)

2008-11-22 Thread John Doty
On Nov 22, 2008, at 4:29 PM, Sean Carter wrote: > So here is the complaint I get from ngspice: ... > Warning: singular matrix: check nodes 2n5245 and 2n5245 > 2n5245 seems an improbable name for a node! This is a clue. In your netlist, I see: > Q1 1 3 2 2N5245 OK, you've run afoul of one of

Re: gEDA-user: Just another minor pcb bug

2008-11-22 Thread Stefan Salewski
Am Samstag, den 22.11.2008, 23:22 + schrieb Peter Clifton: > On Sat, 2008-11-22 at 21:52 +0100, Stefan Salewski wrote: > > pcb 20080202 (GTK) > > > > If Auto enforce DRC clearance is on, lines (traces) starting from a pad > > always snap to one of the pad endpoints. It is impossible to start t

gEDA-user: (no subject)

2008-11-22 Thread Sean Carter
Hi, I have what I hope is a really simple question, which I have been unable to find by rtfm. I have a single fet audio amplifier, I'll put the net file below, and no matter what I do, and I've been poking at this for hours, ngspice can't seem to locate an operating point. First off, the opera

Re: gEDA-user: Just another minor pcb bug

2008-11-22 Thread Peter Clifton
On Sat, 2008-11-22 at 21:52 +0100, Stefan Salewski wrote: > pcb 20080202 (GTK) > > If Auto enforce DRC clearance is on, lines (traces) starting from a pad > always snap to one of the pad endpoints. It is impossible to start the > line from an arbitrary grid point over the pad. Even if you hold do

gEDA-user: Just another minor pcb bug

2008-11-22 Thread Stefan Salewski
pcb 20080202 (GTK) If Auto enforce DRC clearance is on, lines (traces) starting from a pad always snap to one of the pad endpoints. It is impossible to start the line from an arbitrary grid point over the pad. I think this will be a known bug to developers. If not: At http://www.ssalewski.de/tmp

Re: gEDA-user: pcb: parameter escaping for commands (was: Re: pcb/gsch2pcb: problem with special characters in pin names)

2008-11-22 Thread DJ Delorie
> Is the supported syntax described anywhere? Nope. You get to write it! :-) As long as it can do everything in pcb-menu.res it will be fine. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-use

gEDA-user: Mailing list address

2008-11-22 Thread Sascha Silbe
On Sat, Nov 22, 2008 at 03:30:06PM +0100, Sascha Silbe wrote: [...] Sorry for the double post. It appears there a two distinct, but valid addresses for this mailing list. Since my MUA can't know those are identical, it sent the mail to both addresses. The gEDA homepage lists [EMAIL PROTECTED],

gEDA-user: pcb: parameter escaping for commands (was: Re: pcb/gsch2pcb: problem with special characters in pin names)

2008-11-22 Thread Sascha Silbe
On Fri, Nov 14, 2008 at 12:55:30PM -0500, DJ Delorie wrote: pcb currently has no escape mechanism for that. It would be added to src/hid/common/actions.c in hid_parse_actions() if you want to work on it. Looks like it's going to need a full rewrite of that function to implement escaping. Is th

Re: gEDA-user: Overline in Gschem?

2008-11-22 Thread Stefan Salewski
Am Samstag, den 22.11.2008, 04:22 + schrieb Kai-Martin Knaak: > On Mon, 10 Nov 2008 19:48:28 -0500, DJ Delorie wrote: > > >> Just want to know if its possible to overline text in gschem. > > > > Like \_this\_ > > I just put \_this\_ to the wiki... > A related question is: Can/should we us

Re: gEDA-user: Some kind of library manager and hierarchical netlisting

2008-11-22 Thread Paul Tan
John Griessen wrote: > Is the output sets of per page netlists in this case? When you invoke: (hierarchy-traversal "disabled") you can still netlist multi-pages with: gnetlist -g -o foo.out foo1.sch foo2.sch ... The netlist output will be per hierarchy in this case. Best Regards, Paul T

Re: gEDA-user: Selection/drag behavior

2008-11-22 Thread Duncan Drennan
> For me this bug occured about 10 times now, in 100 hours of work. I have > no idea what triggers it. I get this bug a lot. One of the things that I find helps to fix it (other than restarting pcb) is to copy something to the buffer and then start the paste process. This often then shows the outl