X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-Original-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=gmail.com; s=20120113;
	h=date:from:to:subject:message-id:in-reply-to:references:mime-version
	:content-type:content-transfer-encoding;
	bh=d1Ehu3A25s2jskqfEWdY5vTXH+RWyU8ae5WO6qiTPTg=;
	b=M8Bg0dpOgD/JEkgZtfIr6TNjFYDToaiT+gBhvXpxy0bvuVZ2U6/2NtaWyhx6H1xT7l
	h5rrj3zHasREpsiETs3ueoG9Id/kE9+1CdasYixVXefExB5AEK5/l5PdL05YkUcBejvx
	LzzVoAMV1gCR1nX44YYu33TXFwuEa6vkB+Jigm4TjBhfgDjKylf2jfGzTdErWcQOywx2
	95EQwt1uDeMX+MsPAmsetf4ewyhDVoqZzX3UUVfyuAxmaykob+JvO4xNxfLZeUs/syU+
	m8xb1I3Ylbox3DnXylyVYy6u/7ajGWvOfg9DDj47laDDDVBOqqHrwgfndfGuJ1EDqUYD
	hP1Q==
X-Received:	by 10.194.7.197 with SMTP id l5mr5249989wja.153.1441050662595;
	Mon, 31 Aug 2015 12:51:02 -0700 (PDT)
Date:	Mon, 31 Aug 2015 21:50:56 +0200
From:	"Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] back annotation proposal (RFC)
Message-Id:	<20150831215056.ae0d389f0f00128331b8105c@gmail.com>
In-Reply-To:	<55E4715C.6070007@ecosensory.com>
References:	<alpine DOT DEB DOT 2 DOT 00 DOT 1508301838470 DOT 6924 AT igor2priv>
	<201508301802 DOT t7UI2twS031311 AT envy DOT delorie DOT com>
	<CAM2RGhRgPQG2WDFVb0SFvMbypyYKS2oYtD=851WHR6fOB4iWdA AT mail DOT gmail DOT com>
	<201508310341 DOT t7V3fcfh022966 AT envy DOT delorie DOT com>
	<CAM2RGhRcQKdYjR5mKDazQ-TouPK0ydkEgt05tscCcWQh4s0EDQ AT mail DOT gmail DOT com>
	<20150831161636 DOT d99b3f330903ff90376250f2 AT gmail DOT com>
	<55E4715C DOT 6070007 AT ecosensory DOT com>
X-Mailer:	Sylpheed 3.5.0beta1 (GTK+ 2.24.25; x86_64-pc-linux-gnu)
Mime-Version:	1.0
Reply-To:	geda-user AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	geda-user AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

It might be to complicated to handle changes "from any direction" "at any time" during layout but to get stuck at a solution there manual handling in correct order is the only possible implementation is not good either.

If there is no theoretical possibility to tell from a schematic <--> pcb pair in which file the change was done last operator must remember the direction and press the right direction button or as is now run some scripts.



On Mon, 31 Aug 2015 10:23:08 -0500
John Griessen <john AT ecosensory DOT com> wrote:

> On 08/31/2015 09:16 AM, Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com] wrote:
> >   Changes may come from any direction so it is also necessary to know in which directions change should be made. If footprints are different should there be a forward or backward annotation?
> 
> It probably is too complicated a goal to handle changes "from any direction" "at any time" during layout.
> 
> Easier will be to make tools that help "passes" of directed activity succeed.
> 
> As in:
> 1. schematic prelim, 2. place components, 3. Do some layout of non-autorouted power traces,
> 4. Notice some things you forgot and add them to schematic. 5. forward annotate pass, perhaps helped by a make file,
> and/or a makefile and a launcher button for it.  6. Do some layout fixing up the forward annotated footprints,
> 7. autoroute 8.  add some attributes to pcb elements(not even supported yet)  8.5 back annotate pass.
> 9. Do some .sch fixing up, add more forgotten attribs, etc. 10. forward annotate pass, 11. repeat while necessary.
> 

- Raw text -