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:to:references:from:message-id:date:mime-version
	:in-reply-to:content-type:content-transfer-encoding; s=fm1; bh=7
	uDKuXEZMeQoB1UFddOHHqbRGgfXCvPmqVK0AAlFDCA=; b=jmm26EvtVA/QLlV+b
	gl6WWsIJta1myGSWvetzaneN0dXs1sFil8btUs4swSd7eJbmoB6z6OQQQS6m1Gxz
	8kLGYKE9gUQc/6yom0jIdywcnOu9xU1nEiqGZHdmA/1skwq0Xm9iyVwfVzxodyvZ
	0uulukvO9+N6lPCxET1EH2WrpknYNj8jY/y8dlxKk1rJ9yXQ7xuHHySPEYk1nJzU
	HSwFHfIDJkyksiaSB0f3Bch1X3xTDyX4QDzdC09pVGyRxlGoNkpYGWSAxJLNZhPB
	1duptn5AYaMI0aj1IaqgjnZb+cDNDkLtCU5sfF/XIIVl0wzDh9xM6tq2lR9qtlnt
	9wzog==
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=7uDKuXEZMeQoB1UFddOHHqbRGgfXC
	vPmqVK0AAlFDCA=; b=VeAR2qyWqj+UftnHw6PebvfImphi3CkI6nO19aCLb86gN
	B64SPMBstXta4dTGtyKHZeYmhb+di4gTr1el+NXthw92cqSZS8J0TMDHXG5pfIM1
	zFQWcSAN6imT3we1efyNCv106suiXRPgJmTrQU76vFghP+JHStVieefxj8fNmdk8
	ULw7nz/YGA1b+PuRF2ZjZpUFheLFaM4VCwJrhu/dAgFC3Zp8jmBYL9/Xr0O3mgtO
	ILFgu/FOg0h5Y0SHqsWgUYZbWqBnoShM7sP6e9fyobWotBkOzo2e0iuHaNdABJaF
	dl5hLmwDeVFCj3rQZTJZXInT7OKs5devyELkvBrQg==
X-ME-Sender:	<xms:dgEhXmFGLINF7laPxdHLYdTB_gpgoKAphuVWDees-ogTFdqkEX_-QA>
X-ME-Proxy-Cause:	gggruggvucftvghtrhhoucdtuddrgedugedrtdeigddvudcutefuodetggdotefrodftvf
	curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu
	uegrihhlohhuthemuceftddtnecunecujfgurheprhfuvfhfhffkffgfgggjtgfgsehtke
	ertddtfeejnecuhfhrohhmpefiihhrvhhinhcujfgvrhhruceoghhhvghrrhhlsehfrghs
	thhmrghilhdrtghomheqnecukfhppedutdekrddvudehrdduleehrddvtdehnecurfgrrh
	grmhepmhgrihhlfhhrohhmpehghhgvrhhrlhesfhgrshhtmhgrihhlrdgtohhmnecuvehl
	uhhsthgvrhfuihiivgeptd
X-ME-Proxy:	<xmx:dgEhXt6hlvh_y-dG309Pl77O4s5CmMonu56cPUerxTwjbFmVft1EdA>
	<xmx:dgEhXtnoVJGJBmPHAnqFUxFYMSwRm2ByaibpT0W74rAPCdhjvpBMEQ>
	<xmx:dgEhXgT-iTPhXnDShhR-TEeqDV81Dat1fn3y71fJ67zU2LSJvOxNQA>
	<xmx:eAEhXvJ14QDlagZOxIK0dSzWiRJY7rQ74NW6RTpbPxbY8HMLkvCheA>
Subject:	Re: [geda-user] How do I know if symbol is updated?
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>
From:	"Girvin Herr (gherrl AT fastmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Message-ID:	<916382d6-12a8-ccba-7245-c563a75d5103@fastmail.com>
Date:	Thu, 16 Jan 2020 16:35:00 -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:	<alpine.DEB.2.20.2001162207070.8054@nimbus>
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

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 -