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=d9Fe+ssBFyIe2TC/Dv4Dwr04ar7rXduBF+O+qjCtbxU=; b=cAAM1kMq+ziEqFPQWJaIoyrLRerjw8CbFsbhqeJ07LudAIMXNxRsoqvEawPbL78Y0s od9EsSuHc946pOyBJAAC7lGHhUw96dbW5fKcsXH/NBziVWCk/D9bX9QfF7CglTdZjrQb qIIskai/PtBo0zhzA37K2AaFwk34yD9aDJkQItwGnTlNW7ylM5mPA7UCuNc8L4nN1bk/ 303N7qBWggxfD1uPbNR5FicjwhaopMZg8iz8B7bsSXhFVBVrIu0Za9yHyRqv9LiET8Tu 2DimLE5z0WvHIKw3RPjiTzjCvn5IOIIxUNpd73v3clfH+Wku1LrL06m6P4NLv2VEy19v IT9g== X-Received: by 10.194.242.202 with SMTP id ws10mr1825107wjc.47.1445323531704; Mon, 19 Oct 2015 23:45:31 -0700 (PDT) Date: Tue, 20 Oct 2015 08:45:26 +0200 From: "Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Subject: Re: [geda-user] Pin mapping (separate symbols from mappings) Message-Id: <20151020084526.92cecc051d83d4e3d51ee2ec@gmail.com> In-Reply-To: <201510192340.t9JNeo6n020302@envy.delorie.com> References: <20151018204010 DOT 9cce6a231dcc296256e187bd AT gmail DOT com> <201510181843 DOT t9IIhmWo025346 AT envy DOT delorie DOT com> <20151018234424 DOT c0551dad9bef0859130239d9 AT gmail DOT com> <36B94694-F2AC-4A75-A8EB-40A1CE9A534C AT noqsi DOT com> <201510182225 DOT t9IMPkxK032763 AT envy DOT delorie DOT com> <20151019003814 DOT f62620bf0fec77e65104c105 AT gmail DOT com> <201510190242 DOT t9J2gl7w009345 AT envy DOT delorie DOT com> <20151019092555 DOT 46eed4540c2d2044bbeab878 AT gmail DOT com> <1A419AED-FCCA-4B1F-8589-912435534E2E AT noqsi DOT com> <201510191647 DOT t9JGlu4j024585 AT envy DOT delorie DOT com> <041FF42A-691F-4E6B-9DEB-8C6B3C2F3E53 AT noqsi DOT com> <201510191850 DOT t9JIop8Y029095 AT envy DOT delorie DOT com> <201510192055 DOT t9JKt2o6005861 AT envy DOT delorie DOT com> <1E816300-E31E-4B85-B51D-7EAEC5A466BF AT noqsi DOT com> <201510192110 DOT t9JLAFKG007281 AT envy DOT delorie DOT com> <201510192340 DOT t9JNeo6n020302 AT envy DOT delorie DOT com> X-Mailer: Sylpheed 3.5.0beta1 (GTK+ 2.24.25; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 Precedence: bulk > > You also wrote: > > > > > What I want is a way to reliably map an instance of a device with its > > > schematic symbol, without the user having to jump through hoops to > > > satisfy some hidden "rule" about how to create schematics. > > > > How is it hard for a user to understand that symbols need to be > > distinguishable at the schematic level? > > From the user's point of view, they're distinguishable. There's this > one, and that one :-) Why should we force the user to decide > packaging, slotting, and unique numbering, right at the beginning, > when they're just tossing a design together? Even as late as layout, > they could change the packaging and thus change the slotting (for > example, switching from a quad-nand to two dual-nand packages). You are absolutely right packaging, value and slotting is usually not the first step. Nicklas Karlsson