On 10/29/09, DJ Delorie wrote:
>>
>> To be exact, the Ben mode of png exporter, which is
>> somewhat confusing IMVHO (why not in both modes?
>> and what is --as-shown for, then?)
>>
>
> Go ahead and fix it :-)
I did it this summer, when finishing Michael's board.
> --as-shown determines whethe
On Thu, 29 Oct 2009 23:54:30 +, Peter Clifton wrote:
> component
> solder
>
> (other layers are outside the physical stack)
How do additional inner layers come into the mix? Shouldn't the be
granted with layer groups too like:
top
inner_layer1
inner_layer2
bottom
Come to think of it, sil
Er... you're probably right.
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
On Thu, 2009-10-29 at 20:54 -0400, DJ Delorie wrote:
> > -Groups("7,8,c,1,3,4:2,5,6,9,10,s")
> > +Groups("1,3,4,7,8,c:2,5,6,9,10,s")
>
> These are semantically the same.
>
> > I guess I need to identify whether the geiven layer "Layer" is a member
> > of the component or solder _group_.
>
> Righ
> -Groups("7,8,c,1,3,4:2,5,6,9,10,s")
> +Groups("1,3,4,7,8,c:2,5,6,9,10,s")
These are semantically the same.
> I guess I need to identify whether the geiven layer "Layer" is a member
> of the component or solder _group_.
Right, see the png stuff again. Given a layer, you need to determine
whic
On Thu, 2009-10-29 at 20:30 -0400, DJ Delorie wrote:
> Try this board:
>
> http://www.delorie.com/pcb/m3a/board.pcb
>
> It has multiple layers per group, despite being only two sided.
That rendered funny (top via colours) until I "fiddled" with the layer
groups somehow.. looking at the resul
Try this board:
http://www.delorie.com/pcb/m3a/board.pcb
It has multiple layers per group, despite being only two sided.
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
On Thu, 2009-10-29 at 19:55 -0400, DJ Delorie wrote:
> > Just looking at that.. by a definition you mentioned once before..
> > should it in fact be that the above board has physical stackup:
> >
> > component
> > solder
> >
> > (other layers are outside the physical stack)
>
> Well, *yes*.
>
>
> Just looking at that.. by a definition you mentioned once before..
> should it in fact be that the above board has physical stackup:
>
> component
> solder
>
> (other layers are outside the physical stack)
Well, *yes*.
Check out the photo-mode stuff in the png hid; it has to do stuff in
phys
On Thu, 2009-10-29 at 19:52 -0400, DJ Delorie wrote:
> In the photo you included, the physical stackup would be:
>
> component
> solder
> outline
> GND
> power
> signal1
> signal2
> signal3
>
> Note that the lesstif HID uses the same type of layout grid.
>
> If you're iterating from 0..max_layer
In the photo you included, the physical stackup would be:
component
solder
outline
GND
power
signal1
signal2
signal3
Note that the lesstif HID uses the same type of layout grid.
If you're iterating from 0..max_layers, just use it as the array index
into PCB->LayerGroups.Entries[]. The only cat
On Thu, 2009-10-29 at 14:30 -0400, DJ Delorie wrote:
> > I got very (very) ((very)) confused by the code. Since everything is
> > indexed by the same range of numbers, it is easy to make mistakes. I
> > suspect I have made mistakes..
>
> For a physical stackup, you want to iterate through the laye
Peter Clifton wrote:
> What this doesn't define.. is material thickness etc..
That's going to have to come from extra data we don't have in the .pcb format
now.
>> The core needs to know which of the seven traces you just
>> clicked on is the one you meant, and to do that, it needs to know
>
DJ Delorie wrote:
> --as-shown determines whether you use the layer stack as shown, or the
> layer stack as defined by the pcb. It's a "what's on top" setup.
.
.
.
> The core needs to know the stackup, but it doesn't need to know the
> orientation.
Exporting as shown vs. stack up seems tricky.
W
> I got very (very) ((very)) confused by the code. Since everything is
> indexed by the same range of numbers, it is easy to make mistakes. I
> suspect I have made mistakes..
For a physical stackup, you want to iterate through the layer groups,
not the layer stack. For each group, draw all the l
On Thu, 2009-10-29 at 13:20 -0400, DJ Delorie wrote:
> The whole problem of "physical stack" is something we're working on
> separately. I think we've agreed that the physical stack is
> determined by the layer *group* order, from the "component" group
> through the "solder" group.
I got very (ve
The whole problem of "physical stack" is something we're working on
separately. I think we've agreed that the physical stack is
determined by the layer *group* order, from the "component" group
through the "solder" group. This breaks when you have copper outside
those two, like "component, solde
On Thu, 2009-10-29 at 12:58 -0400, DJ Delorie wrote:
> > But now it is not put in the core: both Lesstif and GTK have their own
> > flags for flip-x and flip-y; in it is only ShowSolderSide that is in the
> > core;
> > I don't see why this must not be extented into the future.
>
> ShowSolderSide
>
> To be exact, the Ben mode of png exporter, which is
> somewhat confusing IMVHO (why not in both modes?
> and what is --as-shown for, then?)
>
Go ahead and fix it :-)
--as-shown determines whether you use the layer stack as shown, or the
layer stack as defined by the pcb. It's a "what's on
On 10/29/09, DJ Delorie wrote:
> I think the fundamental problem is that we're mixing core actions
> (like setting the layer stackup) with GUI actions (like which side
> we're viewing).
Sure. I feel this should remain unavoidable.
> That's why the png exporter has it's own "other side" option.
I think the fundamental problem is that we're mixing core actions
(like setting the layer stackup) with GUI actions (like which side
we're viewing). That's why the png exporter has it's own "other side"
option.
Perhaps we could extend the option which sets the visible layer stack
to figure out (
On 10/28/09, Kai-Martin Knaak wrote:
> Unfortunately, the V parameter does not change anything. This is how I
> try to extract a print of the bottom view of the layout:
>
> pcb -x eps \
> --action-string 'SwapSides(V)' \
> --as-shown \
> --layer-stack "comment, outline, elements, bottom" \
On Mon, 26 Oct 2009 21:29:05 -0400, Harry Eaton wrote:
>> 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 i
>> 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,
24 matches
Mail list logo
