Re: gEDA-user: Information on PCB

2009-10-26 Thread Ineiev
On 10/27/09, Ineiev  wrote:
> Try the attached patch; it introduces SwapSides_nogui action for such
Awfully sorry, forgot to commit a typo fix;
and there is no need in `compatible' with GTK and Lesstif hids
arguments parsing.

BTW, it seems to me that it does not really changes the groups
visibility: I press Tab with `component' layer from the component
group active and see the same `component' above all; the pads
are shown from the right side, though. am I doing
something wrong? I stack the patches on top of current master.
From 303def6c5467f63383b58b5fe0353dd97415e647 Mon Sep 17 00:00:00 2001
From: Ineiev 
Date: Tue, 27 Oct 2009 03:05:47 +
Subject: [PATCH] Add SwapSides_nogui action

The action is similar to SwapSides, but it
depends on no real GUI, so can have effect when
running an exporter from command line or
with batch GUI.
---
 src/action.c |   63 ++
 1 files changed, 63 insertions(+), 0 deletions(-)

diff --git a/src/action.c b/src/action.c
index 6b979d3..9ac52e8 100644
--- a/src/action.c
+++ b/src/action.c
@@ -6793,6 +6793,66 @@ ActionPSCalib (int argc, char **argv, int x, int y)
   return 0;
 }
 
+/* -- */
+static const char swapsides_syntax[] =
+"SwapSides_nogui()";
+
+static const char swapsides_help[] =
+"Swaps the side of the board you're looking at.";
+
+/* %start-doc actions SwapSides_nogui
+
+This action shows the opposite side of the board: version
+for scripts when there is no GUI.
+
+Normally, this action changes which pads and silk layer are drawn as
+true silk, and which are drawn as the "invisible" layer.  It also
+determines which solder mask you see.
+
+As a special case, if the layer group for the side you're looking at
+is visible and currently active, and the layer group for the opposite
+is not visible (i.e. disabled), then this action will also swap which
+layer group is visible and active, effectively swapping the ``working
+side'' of the board.
+
+%end-doc */
+
+static int
+SwapSides_nogui (int argc, char **argv, int x, int y)
+{
+  int comp_group = GetLayerGroupNumberByNumber (max_layer + COMPONENT_LAYER);
+  int solder_group = GetLayerGroupNumberByNumber (max_layer + SOLDER_LAYER);
+  int active_group = GetLayerGroupNumberByNumber (LayerStack[0]);
+  int comp_showing =
+PCB->Data->Layer[PCB->LayerGroups.Entries[comp_group][0]].On;
+  int solder_showing =
+PCB->Data->Layer[PCB->LayerGroups.Entries[solder_group][0]].On;
+
+  Settings.ShowSolderSide = !Settings.ShowSolderSide;
+  if (Settings.ShowSolderSide)
+{
+  if (active_group == comp_group && comp_showing && !solder_showing)
+	{
+	  ChangeGroupVisibility (PCB->LayerGroups.Entries[comp_group][0], 0,
+ 0);
+	  ChangeGroupVisibility (PCB->LayerGroups.Entries[solder_group][0], 1,
+ 1);
+	}
+}
+  else
+{
+  if (active_group == solder_group && solder_showing && !comp_showing)
+	{
+	  ChangeGroupVisibility (PCB->LayerGroups.Entries[solder_group][0], 0,
+ 0);
+	  ChangeGroupVisibility (PCB->LayerGroups.Entries[comp_group][0], 1,
+ 1);
+	}
+}
+
+  return 0;
+}
+
 /* --- */
 
 HID_Action action_action_list[] = {
@@ -6931,6 +6991,9 @@ HID_Action action_action_list[] = {
   {"SetValue", 0, ActionSetValue,
setvalue_help, setvalue_syntax}
   ,
+  {"SwapSides_nogui", 0, SwapSides_nogui,
+   swapsides_help, swapsides_syntax}
+  ,
   {"ToggleHideName", 0, ActionToggleHideName,
togglehidename_help, togglehidename_syntax}
   ,
-- 
1.6.4.1



___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user


Re: gEDA-user: Information on PCB

2009-10-26 Thread Ineiev
On 10/27/09, Kai-Martin Knaak  wrote:
> On Mon, 26 Oct 2009 03:52:46 +, Peter Clifton wrote:
> It does -- sort of.
>
> The command
>
> pcb -x eps --action-string 'DISPLAY(Value)' --eps-file foo.eps bar.pcb
>
> does indeed output a layout with values displayed, even if the last saved
> version of pcb showed refdeses.
>
> However, not all actions have the expected effect with the export eps
> export HID. For example,
>   --action-string 'SwapSides()'
> does not seem to change the output in any way. This particular action
> string option works fine if I present it to the GTK HID. My version of
> the patch showed the same room for improvement. Does the action itself
> know whether or not the current HID is a GUI?

Try the attached patch; it introduces SwapSides_nogui action for such
purposes. use it with --as-shown exporter option.

Well, it shows pads from the wrong side, but this is probably an
exporter feature, not the patch one.

Cheers,
Ineiev


0001-Add-SwapSides_nogui-action.patch
Description: Binary data


___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user


gEDA-user: Little lost with netlist and gsch2pcb

2009-10-26 Thread Barry Demers

   Stefan Salewski, thanks for your input.  using xgsch2pcb was quite
   straight forward actually.  I had installed the gEDA suite using
   Ubuntu's Synaptic Package Manager and there it was on my desktop.
   Can't get much simpler than that!  After reading the posts, and
   noticing the "x" on the title bar, I decided that the command line
   package was worth investigating.  I do plan to spend some time with
   the gui version however to see if I can figure out how to better use
   it.
   I have now played a little with PCB and, well, I guess that I need to
   spend more time with it.  I am tempted at this point to use a standard
   cad package for my layouts.  I really like gschem and using gsch2pcb
   to generate a net list is fantastic, love it.  While on PCB, however,
   I spent all kinds of time trying to correct lines that went in wrong
   direction, or wouldn't connect.  The rat's nest was incorrectly drawn,
   didn't have editing features that I thought would help me, layer
   control gave bizarre results.  I do see a great potential, but in the
   meantime, with all the backtracking I ended up doing, using a
   mechanical cad package along with gschem and gsch2pcb  may well be my
   solution , at least until a garner a bit more time with PCB.
   --
   Thank you,
   Barry


___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user


Re: gEDA-user: missing pcb footprints.

2009-10-26 Thread Peter Clifton
On Mon, 2009-10-26 at 11:48 -0700, Mike Bushroe wrote:
> I have been having a lot of trouble with this too. gschem does not
>have a library search routine for foot prints, and so I often create
>schematics that gsch2pcb fails to find many of the foot prints and I
>have to struggle to find the foot prints, sometimes type in huge long
>names that are easy to get wrong, and try to figure which folders both
>gsch2pcb and pcb can find the foot prints in.
>   Is there any plan to add a footprint library to gschem similar to
>the component library, or the foot print library function in pcb?
>Mike

PCB _has_ a footprint library function (unless you're using an old
version!)

http://pcjc2.blogspot.com/2008/01/pcb-library-browser.html

Just keep a copy of PCB open whilst you're making your schematics, and
you're not much more than an alt-tab from finding the right name.




___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user


Re: gEDA-user: pcb flip-sides

2009-10-26 Thread Harry Eaton
>> Can you confirm that version still works as you wanted?
>
> It does -- sort of.
>
> The command
>
> pcb -x eps --action-string 'DISPLAY(Value)' --eps-file foo.eps bar.pcb
>
> does indeed output a layout with values displayed, even if the last saved
> version of pcb showed refdeses.
>
> However, not all actions have the expected effect with the export eps
> export HID. For example,
>        --action-string 'SwapSides()'
> does not seem to change the output in any way. This particular action
> string option works fine if I present it to the GTK HID. My version of
> the patch showed the same room for improvement. Does the action itself
> know whether or not the current HID is a GUI?

You need to use a "V" argument, i.e. SwapSides(V).
With no argument, the lesstif gui does an x-ray view, effectively only
altering the layer stackup. The lesstiff gui supports 4 ways to
SwapSides. The GTK hid should support them as well, but it doesn't.

h.


___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user


Re: gEDA-user: Information on PCB

2009-10-26 Thread Kai-Martin Knaak
On Mon, 26 Oct 2009 03:52:46 +, Peter Clifton wrote:

> Would it be sufficient to start
>> the GUI-HIDs (are there more than two?) with n arbitrary action script
>> and check whether the GUI starts up fine?
> 
> That is one way. (GTK + Lesstif) - although the fact it doesn't crash
> doesn't mean it isn't possible

I just configured pcb  for lesstif with Ineiev's patch and got no crash. 


> I think with Ineiev's modifications, it is pretty safe anyway.. since he
> adjusted the patch such that it only effects non GUI hids.
> 
> Can you confirm that version still works as you wanted?

It does -- sort of. 

The command

pcb -x eps --action-string 'DISPLAY(Value)' --eps-file foo.eps bar.pcb 

does indeed output a layout with values displayed, even if the last saved 
version of pcb showed refdeses. 

However, not all actions have the expected effect with the export eps 
export HID. For example, 
--action-string 'SwapSides()' 
does not seem to change the output in any way. This particular action 
string option works fine if I present it to the GTK HID. My version of 
the patch showed the same room for improvement. Does the action itself 
know whether or not the current HID is a GUI?

---<(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


Re: gEDA-user: PCB+GL testing

2009-10-26 Thread Frank Bergmann
On Sat, 24 Oct 2009 20:52:34 +0100, Peter Clifton wrote:

> Btw, to put it in context... some driver bugs I've triggered in the past
> (on my machine) have killed the Xserver completely! (Now fixed
> upstream!)

Hi Peter,

(I remember your "vague bug report" on intel xorg driver...so here is my...)

running your pcb-gl master-branch on FC11 with intel xorg driver
(2.7.0) crashes my xserver while showing drc window (library window
is ok). It seems to be a bug in the driver, because the same code
on a debian lenny system with radeonhd xorg driver raises no problem.

Frank.



___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user


Re: gEDA-user: missing pcb footprints.

2009-10-26 Thread John Luciani

   I put all of the footprint files (or symlinks) that I use for
   production boards in
   a single directory. I also use descriptive footprint names. To find
   a footprint I use dired mode in EMACS. Very easy to find to
   footprints.
   For semiconductors and some specialized components I add the footprint
   attribute to the schematic symbol (heavy symbols). For these types
   of parts I have yet to use more than two package styles.
   (* jcl *)
   --
   You can't create open hardware with closed EDA tools.
   twitter: [1]http://twitter.com/jluciani
   blog:[2]http://www.luciani.org

References

   1. http://twitter.com/jluciani
   2. http://www.luciani.org/


___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user


Re: gEDA-user: missing pcb footprints.

2009-10-26 Thread Stefan Salewski
On Mon, 2009-10-26 at 11:48 -0700, Mike Bushroe wrote:

>   Is there any plan to add a footprint library to gschem similar to
>the component library, or the foot print library function in pcb?
>Mike
> 

This was discussed a lot on this mailing list -- you may search the
archives.

One "problem" is, that gschem is not PCB centric. gschem -> PCB is one
workflow, among many others, i.e. spice.

A PCB footprint browser or previewer for gschem may not hurt, but there
will not be too much benefit. For people familiar with gEDA/PCB finding
footprints is no problem. (Checking that footprints fit to parts is much
more work -- making printout of layout and putting parts on footprints.)

You may try something like

ste...@amd64-x2 ~ $ locate -i qfp |grep 64

If unsure, load footprint in PCB for inspection.

And see

http://www.luciani.org/geda/pcb/pcb-footprint-list.html

and

http://www.gedasymbols.org/




___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user


Re: gEDA-user: missing pcb footprints.

2009-10-26 Thread Mike Bushroe

   I have been having a lot of trouble with this too. gschem does not
   have a library search routine for foot prints, and so I often create
   schematics that gsch2pcb fails to find many of the foot prints and I
   have to struggle to find the foot prints, sometimes type in huge long
   names that are easy to get wrong, and try to figure which folders both
   gsch2pcb and pcb can find the foot prints in.
  Is there any plan to add a footprint library to gschem similar to
   the component library, or the foot print library function in pcb?
   Mike

 On Mon, 2009-10-26 at 10:07 -0400, Barry Demers wrote:
 >If Peter C. is still interested in having me perform the
 procedure
 >that he outlined, I'd be more than pleased to do so, however,
 I
 >believe, that had xgsch2pcb reported to me that the footprint
 files
 >listed in my schematic attributes were not found/ or not
 usable for
 >whatever reason, then I wouldn't have created my post. I do
 understand
 >now that xgsch2pcb is in beta, so
 Its not really in beta.. although how well it works will depend
 upon
 what version you have!
 The latest version is
 [1]http://geda.seul.org/dist/geda-xgsch2pcb-0.1.3.tar.gz
 Although I think I was slack and didn't get a release announcement
 out.
 If you push the "About" button on xgsch2pcb, you will see what
 version
 it is, please report back.
 Version 1.1.2 onwards reports missing footprints.
 I'd appreciate a copy of the output from xgsch2pcb for interest's
 sake -
 although if you have now fixed your schematic, don't worry about
 doing
 that.
 You might still like to try opening up the .gsch2pcb project file
 with
 xgsch2pcb, as once you have it working, the GUI is nice to use (IMO
 -
 but I'm biased there).
 Best wishes,
 Peter C.
 --
 ___
 geda-user mailing list
 [2]geda-u...@moria.seul.org
 [3]http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
 End of geda-user Digest, Vol 41, Issue 54
 *

References

   1. http://geda.seul.org/dist/geda-xgsch2pcb-0.1.3.tar.gz
   2. mailto:geda-user@moria.seul.org
   3. http://www.seul.org/cgi-bin/mailman/listinfo/geda-user


___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user


Re: gEDA-user: Little lost with netlist and gsch2pcb

2009-10-26 Thread Stefan Salewski
On Mon, 2009-10-26 at 10:07 -0400, Barry Demers wrote:
> At this point I am somewhat
>concerned with my understanding of how the footprint files are
>distributed throughout the file structure.  I am hoping that they are
>arranged in a fashion similar to symbol files with the hierarchy of
>the "rc" files allowing for footprints that I import/create on my
>own.  

Fine that you made some progress with your problems.

I still wonder what did you guide to the graphical tool Xgsch2pcb
instead of the plain command line based. When I read the tutorials they
refer to plan gsch2pcb only. Has this changed?

Getting the right footprints can be a problem for beginners -- I can
remember that I had problems with m4 footprints and invalid file names.
My current project file looks like this:

ste...@amd64-x2 ~ $ cat /mnt/data/stefan/gEDA/DAD/p1
schematics FPGA_Power.sch FPGA_B0B1.sch FPGA_B2B3.sch RAM.sch ADC.sch
TDC.sch Digital_In_A.sch Digital_In_B.sch Digital_In_C.sch
InputDividerCh1.sch InputDividerCh2.sch AmplifierCh1.sch
AmplifierCh2.sch Controller.sch PowerManager.sch DC_DC_Converter.sch
Lin_Regulators.sch Misc.sch AmpCommon.sch
output-name b1
skip-m4
elements-dir /usr/local/share/pcb-symbols-jcl_2008-4-25
elements-dir /home/stefan/gEDA/imported-footprints
elements-dir /mnt/data/stefan/gedasymbols/www/user/stefan_salewski/footprints
elements-dir /home/stefan/gEDA/custom-footprints

I do disable m4 footprints with skip-m4 statement (we can do this
because we have newlib copies for all m4 now). Footprint directories
have priority order -- when equal names occur multiple times, the later
entries in the project file have precedence. So files
in  /home/stefan/gEDA/custom-footprints overwrite other files for my
installation.

Best regards

Stefan Salewski




___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user


Re: gEDA-user: PCB+GL testing

2009-10-26 Thread michalwd1979

> Sounds like GL drivers are going to cause me grief!

And more or less because of me. Sorry.

> No documentation, sorry. I've coded up a very hacky start for what you
> want to do.. Unfortunately, the APIs I wanted to use to make PCB "find"
> the connected objects are burried in find.c and not exposed sufficiently
> for me to call them. I could probably have ripped out and duplicated a
> load of the find.c code in the plugin, but I think it is useful as is.
>
> Find the net you want to join. Hit "F" to "find" the connected objects.
> (Highlighting them in green).
>
> Run action "JoinFound". Presto.
>
> You might want to hack the plugin's code to change the thermal style
> number. IIRC:
>
> 1,2 = square ish thermals
> 3   = solid join thermal
> 4,5 = rounded thermals
>
> 
> SAVE WORK BEFORE RUNNING THIS ONE ;)
> 

Many thanks Peter. I will try to follow Yours code, and possibly learn 
something during the process.

Best Regards,
Michael W.



___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user


Re: gEDA-user: Aperture size for polygon fill

2009-10-26 Thread Stuart Brorson
>> Did you create a zero diameter hole in your design for any reason?
>
> Certainly not intentionally.  Is there any sensible way to search and
> see if there is one somewhere?

The best way is to look at the .pcb file using a text editor.

Or you can export your Gerbers and look at the fab drawing.  One of
the files emitted when you export Gerbers is a fab drawing which will
show all drill diameters and hole locations.  See if that drawing
shows any zero sized drills.

Finally, if you find a D00 aperture defined in your Gerber file,
that's a clue that you've created a zero sized hole.

However, none of this has to do with creating polygons.

Stuart



___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user


Re: gEDA-user: Aperture size for polygon fill

2009-10-26 Thread Windell H. Oskay

On Oct 26, 2009, at 7:58 AM, Stuart Brorson wrote:
>> It may be good to know which version of PCB generated the gerber  
>> file,
>> which version of gerbv you used to inspect it. It may be even more
>> helpful to make the source PCB and the gerber file available for
>> inspection by developers.
>
> ISTR that older versions of PCB would create Gerbers with this error
> if you tried to create a hole with zero diameter.  This bug was fixed
> about a year ago, but if you're using an older version of PCB, then
> you could encounter this problem.

This version is "20081128," so yes it's about a year old.  If this  
sounds like an error that's been fixed since, then we probably don't  
need to worry about it too much.

I'm using fink under MacOS 10.6 and I'm also in the middle of a  
project-- so all signs point to not being able to update in the  
immediate future.  Not a big deal, if I can fix the gerber by hand.

(Speaking of which, can anyone confirm or deny that aperture size is  
unimportant for polygon fill?)

The gerbv is 2.0.1, but it's not gerbv's fault: it has correctly  
identified a real error in the gerber files.

> Did you create a zero diameter hole in your design for any reason?

Certainly not intentionally.  Is there any sensible way to search and  
see if there is one somewhere?



___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user


Re: gEDA-user: Little lost with netlist and gsch2pcb

2009-10-26 Thread Peter Clifton
On Mon, 2009-10-26 at 10:07 -0400, Barry Demers wrote:

>If Peter C. is still interested in having me perform the procedure
>that he outlined, I'd be more than pleased to do so, however, I
>believe, that had xgsch2pcb reported to me that the footprint files
>listed in my schematic attributes were not found/ or not usable for
>whatever reason, then I wouldn't have created my post. I do understand
>now that xgsch2pcb is in beta, so

Its not really in beta.. although how well it works will depend upon
what version you have! 

The latest version is
http://geda.seul.org/dist/geda-xgsch2pcb-0.1.3.tar.gz

Although I think I was slack and didn't get a release announcement out.
If you push the "About" button on xgsch2pcb, you will see what version
it is, please report back.

Version 1.1.2 onwards reports missing footprints.


I'd appreciate a copy of the output from xgsch2pcb for interest's sake -
although if you have now fixed your schematic, don't worry about doing
that.

You might still like to try opening up the .gsch2pcb project file with
xgsch2pcb, as once you have it working, the GUI is nice to use (IMO -
but I'm biased there).


Best wishes,

Peter C.



___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user


Re: gEDA-user: PCB+GL testing

2009-10-26 Thread Peter Clifton
On Mon, 2009-10-26 at 10:04 +0100, michalwd1979 wrote:
> Hello,
> 
> Today I've done all possible tests with new, freshly compiled 3d pcb
> using available PCs and these are the results:
> 
> 1) I can not reproduce "strange" crash with drc window on any machine.
> Was it secret testing of new electromagnetic weapon? I'm living close
> to military shipyard by the way.
> 
> 2) On intel graphics card (composite enabled) I also can not reproduce
> crash in pinout window. Here everything works OK (dri2 in use).
> 
> 3) On intel graphics with composite disabled pcb does not start at
> all: Can not set up gl context, then segmantation fault. Strange, but
> rather related to driver not pcb itself.
> 
> 4) On radeon (composite disabled) there are problems when closing
> pinout window.
> 
> 5) On radeon with composite some drawing errors occur, but this is
> rather problem with driver because I can see similar problems with
> other apps. This is also quite complicated system with 2 graphics
> cards and 3 screens (my favorite).


Sounds like GL drivers are going to cause me grief!

> I've also tried to run teardrops() during these test but this did not
> change anything.

Ok, that is good at least. (Although only running under valgrind would
reliably catch if this causes problems).

> And one question: is there any "plugins documentation" for pcb? In my
> wish list there is something that automatically add thermals tools to
> vias on given net and set "don't clear polygons" flag on tracks. I
> think that I will try to write it myself. I've been looking around for
> a while and did not find anything yet.

No documentation, sorry. I've coded up a very hacky start for what you
want to do.. Unfortunately, the APIs I wanted to use to make PCB "find"
the connected objects are burried in find.c and not exposed sufficiently
for me to call them. I could probably have ripped out and duplicated a
load of the find.c code in the plugin, but I think it is useful as is.

Find the net you want to join. Hit "F" to "find" the connected objects.
(Highlighting them in green).

Run action "JoinFound". Presto.

You might want to hack the plugin's code to change the thermal style
number. IIRC:

1,2 = square ish thermals
3   = solid join thermal
4,5 = rounded thermals


SAVE WORK BEFORE RUNNING THIS ONE ;)


Best wishes,

Peter C.
/* Join found plug-in for PCB
 *
 * Copyright (C) 2009 Peter Clifton 
 *
 * Licensed under the terms of the GNU General Public License, version
 * 2 or later.
 *
 * Compile like this:

 * gcc -Wall -I$HOME/pcbsrc/pcb.clean/src -I$HOME/pcbsrc/pcb.clean -O2 -shared join-found.c -o join-found.so
 *
 *  The resulting join-found.so goes in $HOME/.pcb/plugins/join-found.so
 *
 */

#include 
#include 

#include "global.h"
#include "data.h"
#include "change.h"
#include "undo.h"

#define THERMAL_STYLE 4

static int changed = 0;


/* FIXME: PCB API STOPS ME DOING THIS */
#if 0
static void *
init_line (LayerTypePtr Layer, LineTypePtr Line)
{
  ListStart (LINE_TYPE, NULL, Line, NULL);
  return Line;
}

static void *
init_via (PinTypePtr Via)
{
  ListStart (VIA_TYPE, NULL, Via, NULL);
  return Via;
}

static void *
init_pin (ElementTypePtr Element, PinTypePtr Pin)
{
  ListStart (PIN_TYPE, Element, Pin, NULL);
  return Pin;
}

static void *
init_pad (ElementTypePtr Element, PadTypePtr Pad)
{
  ListStart (PAD_TYPE, Element, Pad, NULL);
  return Pad;
}

static void *
init_arc (LayerTypePtr Layer, ArcTypePtr Arc)
{
  ListStart (ARC_TYPE, Layer, Arc, NULL);
  return Arc;
}

static ObjectFunctionType init_funcs = {
  init_line,
  NULL,
  NULL,
  init_via,
  NULL,
  NULL,
  init_pin,
  init_pad,
  NULL,
  NULL,
  init_arc,
  NULL
};
#endif

static int
joinfound (int argc, char **argv, int x, int y)
{
  int TheFlag = FOUNDFLAG;

  changed = 0;

  /* FIXME: PCB API STOPS ME DOING THIS */
#if 0
  TheFlag = FOUNDFLAG; // | DRCFLAG;
  SaveFindFlag (TheFlag);
  InitConnectionLookup ();
  ResetConnections (False);
  SelectedOperation (init_funcs, False, LINE_TYPE | ARC_TYPE | PIN_TYPE | VIA_TYPE | PAD_TYPE);
  DoIt (True, False);
#endif

  VISIBLELINE_LOOP (PCB->Data);
  {
if (TEST_FLAG (TheFlag, line))
  {
ChangeObjectJoin (LINE_TYPE, layer, line, line);
changed = True;
  }
  }
  ENDALL_LOOP;

  VISIBLEARC_LOOP (PCB->Data);
  {
if (TEST_FLAG (TheFlag, arc))
  {
ChangeObjectJoin (ARC_TYPE, layer, arc, arc);
changed = True;
  }
  }
  ENDALL_LOOP;

  if (PCB->PinOn)
ELEMENT_LOOP (PCB->Data);
  {
PIN_LOOP (element);
{
  if (TEST_FLAG (TheFlag, pin))
{
  ChangeObjectThermal (PIN_TYPE, element, pin, pin, THERMAL_STYLE);
  changed = True;
}
}
END_LOOP;
  }
  END_LOOP;

  if (PCB->ViaOn)
VIA_LOOP (PCB->Data);
  {
if (TEST_FLAG (TheFlag, via))
  {
ChangeObjectThermal (VIA_TYPE, via, via, via, THERMAL_STYLE);
changed = True;
  }
  }
  EN

Re: gEDA-user: Aperture size for polygon fill

2009-10-26 Thread Stuart Brorson
>> A few of the boards that I've been working on (in PCB) have generated
>> gerber files that show errors in gerbv.
>>
>> The error is "Undefined aperture number called out in D code."
>
> If we do a Google search for this error text we find a few similar
> problems.
>
> It may be good to know which version of PCB generated the gerber file,
> which version of gerbv you used to inspect it. It may be even more
> helpful to make the source PCB and the gerber file available for
> inspection by developers.

ISTR that older versions of PCB would create Gerbers with this error
if you tried to create a hole with zero diameter.  This bug was fixed
about a year ago, but if you're using an older version of PCB, then
you could encounter this problem.

Did you create a zero diameter hole in your design for any reason?

Stuart


___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user


gEDA-user: Little lost with netlist and gsch2pcb

2009-10-26 Thread Barry Demers

   My apologies for 2 concurrent same toic posts(How is netlist created \
   Little lost with netlist and gsch2pcb).  Very confusing to readers and
   only slows down process. Allow me to condense both of those to this
   single topic.  Being new to this, I was unaware that the gui version
   of gsch2pcb is actually xgsch2pcb, a beta version, and will henceforth
   treat it as such.  I have, subsequent to that discovery, returned to
   the command line gsch2pcb and have successfully created a useful pcb
   file (footprints with rats nest). Using the command line program
   immediately made me aware that my initial selection of footprint files
   were erroneous and that is an explanation as to why the gui version
   didn't generate a rats nest for me.  At this point I am somewhat
   concerned with my understanding of how the footprint files are
   distributed throughout the file structure.  I am hoping that they are
   arranged in a fashion similar to symbol files with the hierarchy of
   the "rc" files allowing for footprints that I import/create on my
   own.  I need to look at this a bit closer now that I have the layout
   running.
   If Peter C. is still interested in having me perform the procedure
   that he outlined, I'd be more than pleased to do so, however, I
   believe, that had xgsch2pcb reported to me that the footprint files
   listed in my schematic attributes were not found/ or not usable for
   whatever reason, then I wouldn't have created my post. I do understand
   now that xgsch2pcb is in beta, so
   --
   Thank you,
   Barry


___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user


Re: gEDA-user: PCB+GL testing

2009-10-26 Thread DJ Delorie

> And one question: is there any "plugins documentation" for pcb? In
> my wish list there is something that automatically add thermals
> tools to vias on given net and set "don't clear polygons" flag on
> tracks. I think that I will try to write it myself. I've been
> looking around for a while and did not find anything yet.

Not really, they're just shared objects that get linked in at run time
instead of compile time.  You can use pretty much any API in the PCB
core.  IIRC the only "trick" is to have one function named
pcb_plugin_init() that registers all your functionality (actions,
hids, etc).


___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user


Re: gEDA-user: scripts with exporters (was: Information on PCB)

2009-10-26 Thread DJ Delorie

IIRC the original intention of the CRASH macros was that nogui was
used as a template for new HIDs, and the CRASH macros let you know
whick callbacks you needed to implement next.

That we use nogui as an *actual* hid changes the rules somewhat.


___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user


Re: gEDA-user: Aperture size for polygon fill

2009-10-26 Thread Stefan Salewski
On Sun, 2009-10-25 at 20:55 -0700, Windell H. Oskay wrote:
> A few of the boards that I've been working on (in PCB) have generated  
> gerber files that show errors in gerbv.
> 
> The error is "Undefined aperture number called out in D code."

If we do a Google search for this error text we find a few similar
problems.

It may be good to know which version of PCB generated the gerber file,
which version of gerbv you used to inspect it. It may be even more
helpful to make the source PCB and the gerber file available for
inspection by developers.





___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user


Re: gEDA-user: PCB+GL testing

2009-10-26 Thread michalwd1979
Hello,

Today I've done all possible tests with new, freshly compiled 3d pcb using 
available PCs and these are the results:

1) I can not reproduce "strange" crash with drc window on any machine. Was it 
secret testing of new electromagnetic weapon? I'm living close to military 
shipyard by the way.

2) On intel graphics card (composite enabled) I also can not reproduce crash in 
pinout window. Here everything works OK (dri2 in use).

3) On intel graphics with composite disabled pcb does not start at all: Can not 
set up gl context, then segmantation fault. Strange, but rather related to 
driver not pcb itself.

4) On radeon (composite disabled) there are problems when closing pinout window.

5) On radeon with composite some drawing errors occur, but this is rather 
problem with driver because I can see similar problems with other apps. This is 
also quite complicated system with 2 graphics cards and 3 screens (my favorite).

I've also tried to run teardrops() during these test but this did not change 
anything.
And one question: is there any "plugins documentation" for pcb? In my wish list 
there is something that automatically add thermals tools to vias on given net 
and set "don't clear polygons" flag on tracks. I think that I will try to write 
it myself. I've been looking around for a while and did not find anything yet.

Best Regards,
Michael W.


___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user