X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
Date:	Sun, 5 Jun 2016 09:25:34 +0200 (CEST)
X-X-Sender:	igor2 AT igor2priv
To:	"M. J. Everitt (m DOT j DOT everitt AT iee DOT org) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
X-Debug:	to=geda-user AT delorie DOT com from="gedau AT igor2 DOT repo DOT hu"
From:	gedau AT igor2 DOT repo DOT hu
Subject:	Re: [geda-user] pcb: ARC bug
In-Reply-To:	<5753CE50.1020405@iee.org>
Message-ID:	<alpine.DEB.2.00.1606050921200.28818@igor2priv>
References:	<alpine DOT DEB DOT 2 DOT 00 DOT 1606041445000 DOT 28818 AT igor2priv> <575325A6 DOT 5020802 AT iee DOT org> <nj0afa$sel$1 AT ger DOT gmane DOT org> <5753CE50 DOT 1020405 AT iee DOT org>
User-Agent:	Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version:	1.0
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 Sun, 5 Jun 2016, M. J. Everitt (m DOT j DOT everitt AT iee DOT org) [via geda-user AT delorie DOT com] wrote:

> On 05/06/16 05:40, Kai-Martin Knaak wrote:
>> M. J. Everitt wrote:
>>
>>> I've lost PCB elements off the drawing area by accident before ..
>>> the solution of simply enlarging the area, moving items, then
>>> re-adjusting seems perfectly reasonable to me.
>> I fail to see why pcb needs to enforce positioning to the "working
>> area" in the first place. This might have had some merits when the
>> working area was identical with the outline of the resulting board.
>> But these days are long gone.
>>
>> So my preferred solution would be a bit more general:
>>  * Remove the distinction between working area and the rest of the
>> canvas when in comes to positioning of objects.
>>  * Maybe, even remove the notion of the "working area" completely.
>>
>> ---<)kaimartin(>---
>>
> What I mean by the 'working area' is the canvas area described in PCB as
> the "Board size"  in the preferences, not by any outline drawn on the
> screen. Goodness knows what the maximum 'canvas area' can be, and hence
> the limits of where you _could_ theoretically /store/ components
> "out-of-sight" but not removed completely ...
>
> I'm sure one of the devs/coders will probably be able to answer this .. :]

MAX_COORD, which is the half of the largest coordinate that can be 
represented (depends on whether you compiled with 32 or 64 bit coords). 
Should be (2^31)-1 = 2.1 meters or (2^63)-1 = 9223372 kilometers.

- Raw text -