X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.98.4 at av02.lsn.net Message-ID: <55E46E18.7060102@ecosensory.com> Date: Mon, 31 Aug 2015 10:09:12 -0500 From: John Griessen User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.7.0 MIME-Version: 1.0 To: geda-user AT delorie DOT com Subject: Re: [geda-user] back annotation proposal (RFC) References: <201508301802 DOT t7UI2twS031311 AT envy DOT delorie DOT com> <201508310341 DOT t7V3fcfh022966 AT envy DOT delorie DOT com> <20150831111604 DOT 5b1bb421bc015de9a848e8a9 AT gmail DOT com> <55E42456 DOT 5080309 AT jump-ing DOT de> <20150831112032 DOT GA8963 AT visitor2 DOT iram DOT es> <20150831134127 DOT 9dccc4c2563ce7bba5ded79d AT gmail DOT com> In-Reply-To: <20150831134127.9dccc4c2563ce7bba5ded79d@gmail.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Reply-To: geda-user AT delorie DOT com On 08/31/2015 06:41 AM, Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com] wrote: > I have thought a little bit more about the back annotation. Basically there is a syncronization problem then for example a Refdes or footprint could be changed either from gschem or pcb. One possibility to adress this is for pcb to request gschem to make the change as I suggested before with a function like call. If files are used and changes are going both directions I could not figure out how to solve. It's OK to have -backann and -forwann files, each one being one-way.