Oh one update:
** (gschem:2337): CRITICAL **: o_shortest_distance: object 0x8fbf3f8
has bad type
This error showed up just now... I'm suspecting this has something to
do with the net rubber-banding but I'm not sure how to confirm...
Thanks!
~Abhijit
On Tue, Aug 23, 2011 at
On Fri, 19 Aug 2011, Markus Hitter wrote:
Am 15.08.2011 um 22:37 schrieb kqt4a...@comcast.net:
I was especially interested in the drillmill function but I have not been
able to get that to work
I check the box and only get plain drilling
Did you look into the outline G-code file? As
Hey, all. I've used PCB on an off for 10 years and recently have
been getting familiar again with the rest of gEDA which has become a great
set of tools!
Anyway, I've been using a board mill to make 1 and 2-layer
prototypes of typically through-hole components. The trouble is when the
On Tue, 23 Aug 2011 10:36:33 +1000
Stephen Ecob silicon.on.inspirat...@gmail.com wrote:
A few hours in the future, Andrew Poelstra as...@sfu.ca wrote:
On Tue, Aug 23, 2011 at 09:52:19AM +1000, Stephen Ecob wrote:
A few hours in the future, Andrew Poelstra as...@sfu.ca wrote:
* Hide all
On Mon, 22 Aug 2011 20:58:27 -0400
DJ Delorie d...@delorie.com wrote:
if you use pcb with the Lesstif GUI, why?
The lesstif GUI was designed to use very little screen space, leaving
the maximum amount of space for the board.
I just tried out the lesstif pcb GUI. I was surprised to see
On Tue, 23 Aug 2011 02:41:53 -0700
Andrew Poelstra as...@sfu.ca wrote:
On Tue, Aug 23, 2011 at 02:22:25AM +0200, Kai-Martin Knaak wrote:
Andrew Poelstra wrote:
I have implemented the italicized/separated
suggestion. You can see it here:
On Tue, 23 Aug 2011 07:15:54 -0400 (EDT)
Cory Papenfuss papenf...@juneau.me.vt.edu wrote:
Hey, all. I've used PCB on an off for 10 years and recently
have been getting familiar again with the rest of gEDA which has
become a great set of tools!
Anyway, I've been using a board
On Aug 19, 2011, at 7:27 AM, Joshua wrote:
--
It's useful for touch up of a few attributes, but not for the broad changes
you want. The spreadsheet approach really doesn't scale well anyway. If you
have 300 bypass capacitors in a project, it's much more efficient to have a
heavy
Abhijit Kshirsagar abhijit...@gmail.com
writes:
I'm using gschem 1.6.1.20100214 on an Ubuntu 10.10 machine. I'm making a
simple schematic - just a couple of devices and just one page. I find that
it crashes with a Segmentation fault reported on my terminal.
Please upgrade to gEDA 1.6.2, which
Is it required to use hierarchy for multi-page schematics or can I just
continue adding pages in the design ?
You can just keep adding pages, as long as your nets are named. Nets
with the same names get merged when you netlist, as do components with
the same refdes.
On Tue, 23 Aug 2011 09:55:21 -0700
Colin D Bennett co...@gibibit.com wrote:
It would be great if the gtk GUI could provide some options to
increase available screen space
Once I started to work on a patch to have the look and feel of the lesstif GUI
in the GTK GUI. However, I think we should
Thanks. I will try with the newer version.
As of now I think the problem lies in one of the custom components I'm
using - but that should still not cause a segfault right?`
Also,� I'd have liked some inputs on how to debug the problem. Is
there some way of enabling debug logging or
I thought about that... making different footprints that don't
have copper on the component side of the pins. Since that would require
making new footprints for pretty much everything, I was hoping for a
different solution... :) It seems like it would be a relatively common
thing for
On Tue, Aug 23, 2011 at 10:55:23AM -0400, Dan Roganti wrote:
Hello,
I'm trying to find more info about using mulit-page schematics for gEDA
Is it required to use hierarchy for multi-page schematics or can I just
continue adding pages in the design ?
thanks
=Dan
No, it
That would play nice on a dual headed setup.
One of my dream projects is to do a GUI for pcb that uses two or
more monitors, with one monitor heavy on the toolbars and showing an
overview thumber window, and the other monitor being 100% layout.
There were fights against GTK people not to take
On Tue, 23 Aug 2011 14:29:50 -0400
DJ Delorie d...@delorie.com wrote:
That would play nice on a dual headed setup.
One of my dream projects is to do a GUI for pcb that uses two or
more monitors, with one monitor heavy on the toolbars and showing an
overview thumber window, and the other
I put a master roadmap here:
http://geda.seul.org/wiki/pcb:roadmap
I think we've hit some of them, so it needs updating.
The way it works is: things get added to the wish list, then moved up
to the release milestones by the admins as we plan for the future.
with priorities... or the
On Tue, 23 Aug 2011 14:29:50 -0400
DJ Delorie d...@delorie.com wrote:
That would play nice on a dual headed setup.
One of my dream projects is to do a GUI for pcb that uses two or
more monitors, with one monitor heavy on the toolbars and showing an
overview thumber window, and the other
I'm still planning on an OSX Cocoa HID. I haven't gotten very far, but
I do have the very, very beginning. If any one else is interested, let
me know. I'd like to do the same for gschem, but that isn't as modular
just yet.
Mark
On Tue, Aug 23, 2011 at 3:10 PM, DJ Delorie
On Tue, 23 Aug 2011 16:31:49 -0400
DJ Delorie d...@delorie.com wrote:
I think dockable toolbars is the way to go.
+1.
And the ability to store toolbar states in configuration file, or *.pcb
file.
Levente
--
Levente Kovacs
http://levente.logonex.eu
And the ability to store toolbar states in configuration file, or
*.pcb file.
One of the reasons to do my own lesstif tear-offs :-)
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
On Mon, 2011-08-22 at 18:29 +0200, Kai-Martin Knaak wrote:
I subscribed to the mailing list, too. And so did Larry Doolittle, who
already
wrote to the list. :-)
The response by Javier Serrano was interesting:
( http://lists.ohwr.org/sympa/arc/foss-pcb/2011-08/msg3.html )
The
On Mon, 2011-08-22 at 22:54 +0200, Levente Kovacs wrote:
On Mon, 22 Aug 2011 16:51:03 -0400
DJ Delorie d...@delorie.com wrote:
Which GUI ?
GTK
DJ, It broke when you committed a fix for a different issue, I can't
recall exactly which though. I did have a note of the commit which
caused
On Tue, 2011-08-23 at 10:36 +1000, Stephen Ecob wrote:
A few hours in the future, Andrew Poelstra as...@sfu.ca wrote:
On Tue, Aug 23, 2011 at 09:52:19AM +1000, Stephen Ecob wrote:
A few hours in the future, Andrew Poelstra as...@sfu.ca wrote:
* Hide all layers button
* Show all layers
On Mon, 2011-08-22 at 23:45 -0700, Andrew Poelstra wrote:
On Sat, Aug 20, 2011 at 04:41:05PM +0200, Kai-Martin Knaak wrote:
Andrew Poelstra wrote:
Relatedly, why do we let the user select the 'rats' layer?
Can you actually draw with it?
You can draw new connections between components and
On Tue, 2011-08-23 at 13:52 -0400, Cory Papenfuss wrote:
I thought about that... making different footprints that don't
have copper on the component side of the pins. Since that would require
making new footprints for pretty much everything, I was hoping for a
different solution...
On Tue, 2011-08-23 at 23:22 +0530, Abhijit Kshirsagar wrote:
Thanks. I will try with the newer version.
As of now I think the problem lies in one of the custom components I'm
using - but that should still not cause a segfault right?`
No - it should not.
If you can still reproduce it in
On Tue, 2011-08-23 at 16:06 -0400, Mark Anderson wrote:
I'm still planning on an OSX Cocoa HID. I haven't gotten very far, but
I do have the very, very beginning. If any one else is interested, let
me know. I'd like to do the same for gschem, but that isn't as modular
just yet.
On Aug 23, 2011, at 5:14 PM, Peter Clifton wrote:
On Tue, 2011-08-23 at 16:06 -0400, Mark Anderson wrote:
I'm still planning on an OSX Cocoa HID. I haven't gotten very far, but
I do have the very, very beginning. If any one else is interested, let
me know. I'd like to do the same for
Levente Kovacs wrote:
You see your board from component side, and you switch off the copper view of
the other side. Optionally, switch off the far side. Now press tap one time,
and the other side will show up (components on the other side, copper on other
side). Press TAB once again.
Vladimir Zhbanov wrote:
What do you think of it?
Go for it. One howto is enough.
---)kaiamrtin(---
--
Kai-Martin Knaak tel: +49-511-762-2895
Universität Hannover, Inst. für Quantenoptik fax: +49-511-762-2211
Welfengarten 1, 30167 Hannover
DJ Delorie wrote:
Spent some time this week on pushing/fixing LP patches...
LP 699291 - Silk lines were created with the FOUND flag if auto-DRC is on
Nice to see this long term annoyance go for good :-)
Thank you for fixing!
---)kaiamrtin(---
--
Kai-Martin Knaak
I was double checking a pcb layout today and I discovered a rather nasty
gotcha. It seems that gschem and PCB don't agree on which end of a diode
should be pin 1. Gschem views pin 1 as the anode and PCB considers pin 1
to be the cathode. It doesn't prevent you from laying out a board
Dan Roganti wrote:
I'm trying to find more info about using mulit-page schematics for gEDA
Is it required to use hierarchy for multi-page schematics or can I just
continue adding pages in the design ?
If you just add pages, you have to list all of them in the gsch2pcb project
file. That way
Cory Papenfuss wrote:
I thought about that... making different footprints that don't
have copper on the component side of the pins. Since that would require
making new footprints for pretty much everything,
Well, you could do the heavy lifting with an awk script:
If the current line is
Colin D Bennett wrote:
mask has nowhere near the same information content. IMHO, it
is not worth the space savings. Maybe s.mask would be better?
Perhaps it would be best to make the displayed name of the solder mask
layer a user preference.
+1
Just treat it as any other layer name.
DJ Delorie wrote:
I put a master roadmap here:
http://geda.seul.org/wiki/pcb:roadmap
IMHO, a roadmap contains a sequence of milestones, each of which
encompasses clearly defined sub goals. I can only see one sketch of
a milestone, called Next Feature Release. What comes next and
Jared Casper wrote:
I believe the KiCAD folks are also looking at this.
-John
Indeed. The posts to the list that I woke up to this morning took a
frighteningly KiCad-centric turn.
Well, this is, because apparently one of the kicad developers showed up.
Is any of the geda devs going
Peter Clifton wrote:
Even conversion of old legacy Altium designs could be done given access
^
Is this a serious restriction?
Would it be possible for a user of a current altium license to export
to this old legacy format?
to known sample files and
It seems that gschem and PCB don't agree on which end of a diode
should be pin 1.
Welcome back to the transistor problem :-P
I've also noticed that gschem searches the older m4 library first ahead
of the new pcblib. Is there a way to get PCB to use the newlib first?
Probably. I've been
I wouldn't know how to tell PCB that it should look at several
schematics for the import action. Maybe, DJ can add a comment.
Layout-level Attributes:
import::src0 = file1.sch
import::src1 = file2.sch
etc
It's documented in the Import() action in pcb.pdf.
I can only see one sketch of a milestone, called Next Feature
Release.
You're not also checking the bug tracker, though. It *also* has tags
for next/future bug/feature releases. So there are four milestones
coming up, with the next empty one being next incompatible release.
The next release
On 08/22/2011 07:45 AM, Kovacs Levente wrote:
I open up a new schematic, place two instances of 7404-1, edit the
attributes of the second one, promote the slot attribute, edit the
newly-accessible one, change it to 2, save it, save the sheet, exit
gschem, restart, and load the sheet.
I am
Hey all,
The new gtk layer selector is finished for most uses now. If
you want to play with it before it's ready to be published
(which is a few days away still), you can get it here:
git://wpsoftware.net/pcb-andrew.git
branch: layersel
TODO:
- can't change colors
- I'd like to add a
44 matches
Mail list logo
