X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Message-ID: <1407615599.2887.32.camel@AMD64X2>
Subject: Re: [geda-user] How smart is gschems 1.9.1 rubberbanding?
From: Stefan Salewski <mail AT ssalewski DOT de>
To: geda-user AT delorie DOT com
Date: Sat, 09 Aug 2014 22:19:59 +0200
In-Reply-To: <20140809211546.5cebf09a@akka>
References: <1407607347 DOT 2887 DOT 13 DOT camel AT AMD64X2>
	 <20140809211546 DOT 5cebf09a AT akka>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.10.4 
Mime-Version: 1.0
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

On Sat, 2014-08-09 at 21:15 +0200, Kai-Martin Knaak wrote:
> It is on my list of warts ;-)
> Rubber banding should never result in non perpendicular nets. IMHO, it
> would be better to disconnect than to make orthogonal lines slanted.
> The
> disconnect would not go unnoticed, since the disconnected ends get one
> of
> those large, red markers.
> 

Yes, but if we manually reconnect the open end we may do it wrong. 

> Good rubberbanding would involve a bunch of heuristics. There are some
> non trivial constraints. E.g. new segments should never result in
> shortened connections. Sometimes it is better to introduce an
> additional
> segment in the middle. Sometimes, the segment should be at the end of

That is an interesting point.

Generally on-the-fly netlist generation would be good, to detect
whenever netlist has changed unintentionally by moving objects around.
For gschem that may be no problem -- for me it is currently, I have no
netlist generating code, and it was never my goal to write it, because
PCB can import schematics directly, and for people needing a netlist
export gnetlist is available. At least I will do it not now, maybe
later, after the first working release of.