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=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:content-type;
	bh=ecxEhQzufEKTsprxWumxBBWOGD2SN82eH2wpSKfFR8o=;
	b=lcU26phbCKiBKdpbhhLOjZl+dp8Du4alCWsND9Y8Jov9kjtzT5/IIxZEhL3FonxVCD
	Q47KduMEK2M1YOeRwkhClT9OXibrzLtZcIW5h4tQPV3IfK4D1Obf4qSzFwFgunnH+S+o
	KQr6fupHMgQwj1as9ARZ24qYGREdMqw5hahPwQeTEoxQCKOnDYDgnVZdxT2zDQ6ZDBVK
	wkAAaWKZFBa9DJxUjofEZ4T3hZk5bqcWyBsLqcfyiu919RGK2yzh+Z/SqJGRLL3oRUIC
	0DTNzL4zHKHRIb7MBEsmCxpU9NdR2++AdNGGIC5wkXvMMD/V/t4TB0/UIK6ALBWFNynM
	MGTw==
MIME-Version:	1.0
X-Received:	by 10.152.26.163 with SMTP id m3mr33154128lag.86.1437486289459;
	Tue, 21 Jul 2015 06:44:49 -0700 (PDT)
In-Reply-To:	<alpine.DEB.2.11.1507211410260.2035@nimbus>
References:	<1437430095 DOT 1321 DOT 17 DOT camel AT ssalewski DOT de>
	<alpine DOT DEB DOT 2 DOT 11 DOT 1507211410260 DOT 2035 AT nimbus>
Date:	Tue, 21 Jul 2015 13:44:49 +0000
Message-ID:	<CAM2RGhRpbuFj5sagLZQok4AxYM+oLT1sjXYgjWV26YanFP4hog@mail.gmail.com>
Subject:	Re: [geda-user] My gschem 1.9.1 is breaking rubber bands
From:	"Evan Foss (evanfoss AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	geda-user AT delorie DOT 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

On Tue, Jul 21, 2015 at 12:19 PM, Roland Lutz <rlutz AT hedmen DOT org> wrote:
> On Tue, 21 Jul 2015, Stefan Salewski wrote:
>>
>> Is so, there should really be a "netlist modified warning": A widget or
>> menu item which can generates a current netlist in RAM, and shows a warning
>> when that netlist is changed. That feature would allow fully save graphical
>> cleanup of of schematics. I think I suggested that already in the past.
>
>
> This is a nice idea.  I imagine a "netlist changes since last save" window
> where you can see a diff of the netlists and can decide if the changes are
> intentional or accidental.

Isn't that the sort of thing the log window is there for?

> A simplified version of this would be an automatic re-generation of a
> netlist file for each schematic, so you would notice on commit if the
> netlist changed.  This would also have the nice effect of treating the
> netlist as a first-class source object.
>
> Roland
>



-- 
Home
http://evanfoss.googlepages.com/
Work
http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/

- Raw text -