Hello, all.
I've made a script which can be used to print all open schematics to
files in one step. You could either use Execute script in gschem menu
to run it as is or uncomment last string to run it as standalone script
using command 'gschem -s printall.scm -p schematic1.sch schematic2.sch
Hello everyone,
it's time for another pcb crash report. :-)
Steps to reproduce:
1. open the board attached to this e-mail
2. press Tab to switch to the solder side view
3. position the cursor above the via and press v
Sometimes pcb crashes on step 2, but it always crashes on step 3.
I don't get a crash, but 'v' does move the board completely outside
the viewport.
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
it's time for another pcb crash report. :-)
Also, please file all bug reports in launchpad:
https://bugs.launchpad.net/pcb
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
On Wed, Sep 14, 2011 at 09:54:55PM +0400, Vladimir Zhbanov wrote:
Hello, all.
I've made a script which can be used to print all open schematics to
files in one step. You could either use Execute script in gschem menu
to run it as is or uncomment last string to run it as standalone script
DJ Delorie wrote:
File - Preferences - Library - Add a library path
then Restart program for changes to take effect.
This is how it works in Linux too, though.
Most linux users don't see this as it is automatically done by the post
install scripts of their distro. They choose geda in the
Most linux users don't see this as it is automatically done by the post
install scripts of their distro. They choose geda in the package manager,
press install and are done. No need to add paths to anything.
You're talking about two different things now.
PCB's installed library is
On Wed, Sep 14, 2011 at 02:25:54PM -0400, DJ Delorie wrote:
Also, please file all bug reports in launchpad:
https://bugs.launchpad.net/pcb
Right.
This bug is now tracked at https://bugs.launchpad.net/pcb/+bug/850311.
--
Ivan Stankovic, poke...@fly.srk.fer.hr
Protect your digital freedom and
The last part of tracing is to write some kind of netlist or list of
connections, which probably is pretty much the same as
back-annotation. From what I find in the mailing list and the
documentation, there is not very much support for this in pcb at the
moment, or am I missing something. It
PCB's netlist is readily available within pcb's innards, and easily
parsable out of the *.pcb file. So far nobody's needed it so there's
no command to extract it, that's all.
If you have a specific format you need it in, your best choice is to
write an exporter for it, then you can extract it
Have you tried the old PCB autorouter? When I tried it years ago
it worked not really good, but in the meantime the author has made some
serious improvements, as he told us.
Yes, the normal autorouter is what I settled for. The result was reasonable
and completely acceptable for this
On Wed, 2011-09-14 at 21:46 +0200, Ivan Stankovic wrote:
On Wed, Sep 14, 2011 at 02:25:54PM -0400, DJ Delorie wrote:
Also, please file all bug reports in launchpad:
https://bugs.launchpad.net/pcb
Right.
This bug is now tracked at https://bugs.launchpad.net/pcb/+bug/850311.
Should be
On Wed, 2011-09-14 at 16:41 -0400, DJ Delorie wrote:
PCB's netlist is readily available within pcb's innards, and easily
parsable out of the *.pcb file. So far nobody's needed it so there's
no command to extract it, that's all.
If you have a specific format you need it in, your best choice
If you wanted to extract the as-built connectivity from a layout
(possibly one without a netlist specified in the PCB file), one
would have to re-construct a new netlist by tracking connectivity as
per the F key to find connected copper.
I would think PCB would already have one of those,
14 matches
Mail list logo
