X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=google.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:x-gm-message-state;
        bh=Ihv7bXerlgk3YZRFa8VDXdNJBNe1PQm3X9inXubPgRI=;
        b=Pwgkagt+npXJWzvRFe4WFlcTI3sruWFlC5oDPyQg09Unz+kHttZ+y9WeATYHNZjkvJ
         BjSoZyn2R+rcKhOGdNxiUcoyHk5tfeGaGIQi/AQmbQuHvontXgQdeXquDeyt4dhKivkb
         xt1UpSvwfgDEOa0M15d8ZPfeFXlDOSrFgqlg7+ewAj+wcdy4wKs9vrNiyEXUGaQiGqgn
         2CexXmFhlygD7FGYrUcvrc42oXLtqSuNutujXDKxvGqz7C/KDn175b48wI6jwCHy2/O4
         FAmZB65AYDd9kXDYpNKBZtBQgOywzFSTylSZxGa2KupoqYTweYB76iHFTAPEvsvdS2qQ
         tpww==
MIME-Version: 1.0
In-Reply-To: <508BBF8D.5070309@jump-ing.de>
References: <508BBF8D DOT 5070309 AT jump-ing DOT de>
Date: Sun, 28 Oct 2012 20:55:34 -0700
Message-ID: <CAN0Jx--s+2ag-VVpw5gvo-wZWBi-iNsj+B9eN6+tRy_u5e6pyg@mail.gmail.com>
Subject: Re: [geda-user] RFC: storing cursor position in PCB files
From: Russell Dill <Russ DOT Dill AT asu DOT edu>
To: geda-user AT delorie DOT com
Content-Type: text/plain; charset=UTF-8
X-Gm-Message-State: ALoCoQmHRfdkZGbjs6T4bnngXP9XDaD5TmerKL5KUmOUDo/7Uz8IL0L2kbbndnqSx2fgXwZrT1Lj
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, Oct 27, 2012 at 4:03 AM, Markus Hitter <mah AT jump-ing DOT de> wrote:
>
> Recently I get repeatedly unneccessary(?) merge/cherry-pick conflicts with
> line 9 of .pcb files. This line typically reads something like
>
> Cursor[7500 30000 6.000000]  (latest release) or
> Cursor[625.00mil 25.00mil 6.000000]  (current git master)
>
> Apparently, the last position of the cursor is stored here, which is pretty
> much arbitrary, so it changes on every save.
>
> Now I can't imagine how a stored cursor position might be useful for
> anything. When viewing the file it's overridden as soon as the mouse enters
> the viewing area. If there's no use, I'd like to remove that entry to reduce
> the conflict potential.

Ack!