X-Authentication-Warning:	delorie.com: mail set sender to geda-help-bounces using -f
X-Recipient:	geda-help AT delorie DOT com
Date:	Sat, 30 Jul 2016 16:44:48 +0200
From:	"Smilie (smilie AT posteo DOT de) [via geda-help AT delorie DOT com]" <geda-help AT delorie DOT com>
To:	geda-help AT delorie DOT com
Subject:	Re: [geda-help] pcb: blind via
Message-ID:	<20160730164448.6267feca@debian.olsr>
In-Reply-To:	<201607291441.u6TEfqwR013670@envy.delorie.com>
References:	<20160728160657 DOT 7f68f787 AT debian>
	<20160728174027 DOT 453b2b41 AT debian DOT olsr>
	<20160728192015 DOT 4fc84ce8 AT debian DOT olsr>
	<201607282248 DOT u6SMmTxw006065 AT envy DOT delorie DOT com>
	<20160729105443 DOT 7008f31e AT debian>
	<201607291441 DOT u6TEfqwR013670 AT envy DOT delorie DOT com>
Organization:	Individuum auf blauem Planet
X-Mailer:	Claws Mail 3.13.2 (GTK+ 2.24.30; x86_64-pc-linux-gnu)
MIME-Version:	1.0
Reply-To:	geda-help AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	geda-help AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

Am Fri, 29 Jul 2016 10:41:52 -0400
schrieb DJ Delorie <dj AT delorie DOT com>:

> > 1. You can use the Thrm button for rotate the parameter.
> > 2. May be, you change this attribute in circle with the THRM-Form.
> > 1. If it is possible, we should it make backward compatible.
> > 2. We need a option per via tho disable several layers.  
> 
> I mean, can you have a via between *any* two layers, or just specific
> layers according to how the fab builds the board?  Can you stack blind
> vias over each other?  If so, how does the user know which via is
> selected?

The Fabs are different in her performance. Mainly you can have VIAs
between every arbitrary layers. You can also have two VIAs on the same
point in different layers. You just need the drill-file for each
Via-Type (Layer_3-5.drill, Layer_1-2.drill ). 
The Software-Tool shall be universal at all.
The fabs do, what we wish.


See this:
https://www.ucamco.com/en/file-formats/gerber/demo-1
This is not a limit for fantasy.



> 
> It's one thing to say "we'll use a tool", it's another to think
> through *how* we'll use the tool, and if that covers all the things we
> need.
> 
> > > * What about DRC, optimizers, autorouters, and exporters?  Do they
> > >   need changes to handle them?  
> > 
> > This is the only real problem (: and hard work.
> > How do you serve the Info for:
> >  DRC,
> >  autorouter,
> >  Lookup Connection.  
> 
> Most of DRC is in find.c
> 
> autorouter is in autoroute.c
> 
> lookup connection is also find.c
> 
> Probably also need to worry about crosshair.c (for auto-drc) and djopt
> (optimizer).
> 
> And, obviously, draw.c and the exporters :-)


I see, this are many things.
The Exporter is one of the easy problem.

What is about the RAT?

- Raw text -