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=fastmail.com; h=
	reply-to:subject:from:to:references:message-id:date:mime-version
	:in-reply-to:content-type:content-transfer-encoding; s=fm1; bh=X
	IbWsz7XXjrp6H+UunHmbutGFK5+3+PE5JglJM3E4kg=; b=DMXedg1do6WiiJ5MA
	Nb09GNqPuM821avyboahf6DOgadBWRVf3M2qo4TwaL+ucHB55IDtCA/NHqpSaKYz
	JPa6RMh2XejMgtwjz59woc7sKUIZJ8eOo3flYjY6f+cEBS+K4XYF+g/X9GTObd/y
	uKPn52nzVNvTVRBJ3KnsyLVG8RnJmeSel7NvApEgQ2prhAuQILWtCJuG5U9yVhIV
	fpeYcS/Gavg62+jISEqjaA1/vx3boIqiIwYOamQ9FT3SZXNwt92OIEb6ujzphPuz
	ehh6EDNxzovjWuuliYN7+XAf6Sw4GP2usKiZbeiJde7nf3/DxUPQdemL6Bx0F+pX
	ogOeQ==
X-Original-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=
	messagingengine.com; h=content-transfer-encoding:content-type
	:date:from:in-reply-to:message-id:mime-version:references
	:reply-to:subject:to:x-me-proxy:x-me-proxy:x-me-sender
	:x-me-sender:x-sasl-enc; s=fm1; bh=XIbWsz7XXjrp6H+UunHmbutGFK5+3
	+PE5JglJM3E4kg=; b=Xuyh3oALOgoy6INPg96SLWbd+uwaxBbsccf4J2KDzQkQM
	UW5+TBpn7X3GfpVW/8BABmgmUxD7XY0GTrgXr2bUeONk9e2HMMTBG2X86D4VxV0z
	WXNN4fpHsULI1J43h6+CG19UjdSrkxc2XF3YByrzn63LYvq+OZHKFCHmLk9dVQ1N
	0dRuIxUu5t24rsa/YqAYsPr/jXshoJ6TrLDYks4/juK9mCitiSYIjYHX+FycA0si
	K9+ijkBrrXixP/A3iZcvaqf3DZRU12vzVAhOXS1PWpH9VcxhyiJipImRT7Y6p658
	h8lMKURvs6sasutQJQLnXsoqd5OLKL1Ubuqe+raLg==
X-ME-Sender:	<xms:Hy8iXlZh_YuBTDrMlrrLt8Tl7BID4U_VKnTanmFG9j2M65WM_ZdqrA>
X-ME-Proxy-Cause:	gggruggvucftvghtrhhoucdtuddrgedugedrtdekgdeivdcutefuodetggdotefrodftvf
	curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu
	uegrihhlohhuthemuceftddtnecunecujfgurheprhfuhffvfhfkffgfgggjtgfgsehtke
	ertddtfeejnecuhfhrohhmpefiihhrvhhinhcujfgvrhhruceoghhhvghrrhhlsehfrghs
	thhmrghilhdrtghomheqnecukfhppedutdekrddvudehrdduleehrddvtdehnecurfgrrh
	grmhepmhgrihhlfhhrohhmpehghhgvrhhrlhesfhgrshhtmhgrihhlrdgtohhmnecuvehl
	uhhsthgvrhfuihiivgeptd
X-ME-Proxy:	<xmx:Hy8iXoGM6io3ISFsFo5g1IGH7YLp0BytF8DNxtqokFqVwteWT_BC9w>
	<xmx:Hy8iXu2wdzE-u3Cof6EMS-vQ43_h2i1gXel8BMgJzdwkaBdzT5ALpw>
	<xmx:Hy8iXocDVIfRDROtkJgqnFZuJE8MT-HD7YUrN8p8jkAElXgjOyaKiQ>
	<xmx:Hy8iXrV0RzSj9I0ZYnlhakQJamb_O4MvtcMoWnV47UcJ7AtzguFwPw>
Subject:	Re: [geda-user] How do I know if symbol is updated?
From:	"Girvin Herr (gherrl AT fastmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	geda-user AT delorie DOT com
References:	<8839beff-f9b7-404b-23d1-c3772ffbb6b3 AT fastmail DOT com>
	<alpine DOT DEB DOT 2 DOT 20 DOT 2001162207070 DOT 8054 AT nimbus>
	<916382d6-12a8-ccba-7245-c563a75d5103 AT fastmail DOT com>
Message-ID:	<0059d631-4959-a053-bbdf-b2b8f6fdbf6d@fastmail.com>
Date:	Fri, 17 Jan 2020 14:02:04 -0800
User-Agent:	Mozilla/5.0 (X11; Linux i686; rv:68.0) Gecko/20100101
	Thunderbird/68.3.1
MIME-Version:	1.0
In-Reply-To:	<916382d6-12a8-ccba-7245-c563a75d5103@fastmail.com>
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

Although in my last posting yesterday, I said there were two options to 
remove the symbol version warning message. Now it looks like there is 
only one reliable option. After I posted that message, I continued to 
use E-U to update my offending symbols. However, I noticed that 
sometimes, E-U does not promote the symversion attribute even though 
there is not an existing promoted symversion attribute. I do not know 
why that is happening. Therefore, I must assume the only reliable option 
is to use option #2 - to manually delete any existing promoted 
symversion attribute and then promote the correct symversion attribute. 
That seems to work every time.

Girvin


On 1/16/20 4:35 PM, Girvin Herr wrote:
> Roland,
>
> Thanks for your prompt reply.
>
> First, I must say that I do like 1.10.0. It is a great improvement 
> over 1.8.2.
>
> See replies and comments below >...
>
>
> On 1/16/20 1:37 PM, Roland Lutz wrote:
>> Hi Girvin,
>>
>> On Thu, 16 Jan 2020, Girvin Herr (gherrl AT fastmail DOT com) [via 
>> geda-user AT delorie DOT com] wrote:
>>> I see that the symbol update command has changed from ep to EU
>>
>> this was changed between 1.9.1 and 1.9.2 (commit f73fb35).  As far as 
>> I can tell, this isn't related to any changes to the symbol update 
>> mechanism itself.
> I have not used the 1.9.x versions because they were never listed as 
> stable to my knowledge. The last version I used was 1.8.2.
>>
>>> however, the previous gschem version reported the symbol update 
>>> command status and this new version reports nothing, not even in the 
>>> status window, as if nothing was done . How do I confirm the symbol 
>>> has been updated without closing and re-opening the schematic to see 
>>> if the warnings go away?
>>
>> What kind of feedback would you expect?  Could you maybe include a 
>> screenshot of the kind of feedback you are used from earlier versions 
>> of gschem?
>>> I just looked at the updated symbol attributes and there was a 
>>> promoted symversion attribute added which another instantiation of 
>>> the same symbol which is not updated, does not have. I then updated 
>>> the un-updated symbol instantiation and the promoted symversion 
>>> attribute appeared. Is this the proper way to check it?
>>
>> I think you may be confusing two concepts here:
>>
>> - "Object / Update Symbol" ("E U") re-loads the symbol associated 
>> with a component.  If the component is referenced (the default), this 
>> isn't necessary unless the symbol has been modified since opening the 
>> file.  As a side effect, it promotes eligible attributes which are 
>> present in the symbol but not yet attached to the component, 
>> including symversion=.
>
> Confirmation of this:
>
> I loaded just sheet 1 of my schematic and verified I still got the 
> symbol version warning on one symbol instance. I used E-U on the 
> offending symbol, but the already-promoted symversion attribute would 
> not change. If symversion is already promoted, E-U will not change it. 
> E-U will only promote symversion if it is not already promoted. That 
> makes some sense, I guess, but I think there should be a warning about 
> not doing it or even asking to do it or not. So, it looks like in the 
> cases where symversion is already promoted, just using E-U on the 
> symbol will not stop the symbol version warnings when the schematic is 
> loaded. More than just E-U is needed:
>
> I then deleted the symbol's promoted symversion attribute and promoted 
> the unpromoted symversion attribute and then the promoted symversion 
> took on the correct value. I saved and reloaded the schematic and now 
> the version warning is gone. So, it looks like E-U is not doing the 
> whole job. And it is not doing it without any warnings in the status 
> window. It definitely looks like more warning/status messages are 
> needed. Until then, when updating a symbol instance with E-U, the 
> attributes tab must be open and the symbol checked for an already 
> promoted symversion attribute. If it is there, it must be deleted and 
> the un-promoted symversion attribute promoted. Alternately, the 
> promoted symversion attribute could be deleted before using E-U. Then 
> E-U would promote symversion for you.
>
>>
>> - When a schematic file is opened, the symversion= attributes 
>> attached to components are compared to the symversion= attributes 
>> inherited from the corresponding symbols.  If a mismatch is detected, 
>> gschem assumes that the symbol file has been changed since the 
>> schematic was created and issues a warning.
>>
>> The purpose of the symversion= mismatch warning is to make you aware 
>> that the symbols *have* changed.  You should make sure the 
>> connections and attributes are still correct, then update the 
>> symversion= attributes attached to the components in order to make 
>> the warnings go away.
>> Roland
>>
> BTW: I tried to reinstall 1.8.2 and it would not run. Looks like 
> problems reading (parsing) the config files. Did 1.10.0 change the 
> config files, making them incompatible with older versions?
>
> Whew! I removed 1.8.2 and reinstalled 1.10.0 and it is still working, 
> thank goodness!
> So, it looks like I cannot give you any screenshots from 1.8.2.
>
> Thanks.
>
> Girvin
>
>

- Raw text -