X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Virus-Scanned: amavisd-new at neurotica.com X-NSA-prism-xkeyscore: I do not consent to surveillance, prick X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=neurotica.com; s=default; t=1436465763; bh=5VCQ7A8eQ3eMmEFdO69w/b5vAtlFUyK/es+EMoy81VE=; h=Date:From:To:Subject:References:In-Reply-To; b=MLZ4/JHj24e26YYOCt4HWApmJdJvWEx5CwaZQtLetLzxVoE/+xSWgCUTsmek6e79c bRvrddcg37b/M4/Qb2HbGwvJ3ebaLOuJimSve5D7gUPhPX4nC6748VXvwFnau8V1VQ XNRa0o12EK/+pYZgBky74uLUrQMUWvRh7ehFM1bk= Message-ID: <559EBA61.7040402@neurotica.com> Date: Thu, 09 Jul 2015 14:16:01 -0400 From: "Dave McGuire (mcguire AT neurotica DOT com) [via geda-user AT delorie DOT com]" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: geda-user AT delorie DOT com Subject: Re: [geda-user] Back annotation References: <44FED82A-8277-427B-87A8-FBC5E9A3D0E5 AT noqsi DOT com> <11988591-8CA7-4132-B14A-21A53895E63E AT noqsi DOT com> <559E8975 DOT 9050805 AT neurotica DOT com> <818298FE-2D6E-4B60-98E4-CAA8B37230CF AT noqsi DOT com> In-Reply-To: <818298FE-2D6E-4B60-98E4-CAA8B37230CF@noqsi.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id t69IGavS012607 Reply-To: geda-user AT delorie DOT com On 07/09/2015 12:23 PM, John Doty wrote: >>>>> If you’re just making changes until a diff shows nothing, it doesn’t matter whether you make them upstream or downstream. Just quit when you have a match! >>>> >>>> This sounds reasonable to me. So the common denominator is to load a "target netlist" into gschem and show the differences between the current state and the target state, either by highlighting them in the schematic or by showing a diff? This shouldn't be too difficult to implement. >>> >>> Not into gschem. Keep gschem clean, please. I just displayed a diff in a terminal window. >> >> Why are you assuming that adding this (or anything else!) will >> automatically make gschem "dirty"? >> >> First, maybe such new functionality could be made a configure-time >> option. Second, and perhaps more intuitively...if you don't like a new >> feature, don't use it. > > Features interact, so misfeatures get in the way. Box selection of groups of components in gschem used to be simple and straightforward, but added “features” have made it much more difficult. Ok, fair enough. I could be wrong, but that sounds like a bug to me. -Dave -- Dave McGuire, AK4HZ New Kensington, PA