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:from:date:message-id:subject:to
         :content-transfer-encoding;
        bh=TyGoHUusmRgTbctkjHys/KoLughMpIdi+MJpU0Zc2/k=;
        b=WAljwmijQi9qepPSiNcPz6/UVUygbU83SFwTnaJCBvCZHouhqgqPC6/xpD1yXxBRwL
         Jr5Lq1GuUqF3K9jbtspmxOUntd+wgAGi87L4U+r26DHdn7MDapdA1/3gA44T6hbsTrIJ
         J1CCVYwg8E4bDKUfcz1Nuwu9aGGIvpWtI1msadxxPT0VgfLobL81xfzzge3pwUppHoPS
         Uw4SSOK0wLJHFSEEZhGBHJoQYinyqJMNSrSs3pVt9MXxAnq6IH11qtruTQm+LGF7zAwE
         w3j7yJkmJNdnPBI0EPHZyve49OrAMns78f5oshWQyYeJ37fxpQ8yltneGlY4YxoxS/EI
         d69w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:mime-version:in-reply-to:references:from:date
         :message-id:subject:to:content-transfer-encoding;
        bh=TyGoHUusmRgTbctkjHys/KoLughMpIdi+MJpU0Zc2/k=;
        b=GwTjFO6gMw7lASRSVDxI/Lr0yLLdUBMYregPtc8MEai353elua98951xA4vEIQmHJr
         0E47gpFVY7D1n0jUkzrZvfXyu4Yy57LQ1uHqhdUUXv+b3Lw1hHWYurzvWyZwl97cix8k
         Mkuns4PuxOYOV76Fba8/8atlmP/hKpvbqyVfQq6kZYzYnZ1zCyZqXhzro5hCLjTWGnTi
         tX67um4xkd+vakhm9DCcH97jkjH3KHQTNwOG0J3ZCW2H+uCNVyhJZqadpmcYNMdKMajd
         kZRmLe7IrVGcLk84yVg9LKRVOv6E8RaOpUahp5ssaxwb3fMj7nRvESzkkoZMLnE2Jd3e
         n80w==
X-Gm-Message-State: ABUngveKJv0/K6H5dO5/1o6E2mTWyU27hICYa2jQhUrVSjW0gfqNituUwVQ6CKTOFWEjm2oey/awkuxDsF0UiQ==
X-Received: by 10.129.178.5 with SMTP id q5mr8019883ywh.280.1477182984139;
 Sat, 22 Oct 2016 17:36:24 -0700 (PDT)
MIME-Version: 1.0
In-Reply-To: <141F9C23-F141-42FE-A760-834BBDAA7C2F@qux.com>
References: <1477080832 DOT 2909 DOT 106 DOT camel AT linetec> <201610212041 DOT u9LKfw5r031245 AT envy DOT delorie DOT com>
 <1477089908 DOT 2909 DOT 123 DOT camel AT linetec> <s6nbmycyci8 DOT fsf AT blaulicht DOT dmz DOT brux>
 <1477129015 DOT 2909 DOT 130 DOT camel AT linetec> <141F9C23-F141-42FE-A760-834BBDAA7C2F AT qux DOT com>
From: "dmn (graahnul DOT grom AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Date: Sun, 23 Oct 2016 03:36:23 +0300
Message-ID: <CAAKZVJnZFhwf1SJpiMirG3YGb6gwcRq0+x=kdf49fRpLmGh=Ew@mail.gmail.com>
Subject: Re: [geda-user] Annoying object selection behaviour in gschem > 1.6.2
To: geda-user AT delorie DOT com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id u9N0aSSD030372
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 10/22/16, Roger Williams (roger AT qux DOT com) [via
geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
> In 1.8.2, after copying an object, the old object remains selected, rather
> than the selection shifting to the the copy as in ≤ 1.6.2. This not only
> reduces productivity, but it breaks a long-standing convention in CAD that
> the selection shifts to the copy.

Agree.

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;
; Shift selection to pasted objects:
;

( use-modules ( gschem selection ) )
( use-modules ( gschem window    ) )
( use-modules ( gschem hook      ) )

( define ( on_paste objs )

    ( for-each
    ( lambda( obj )
        ( deselect-object! obj )
    )
    ( page-selection (active-page) )
    )

    ( for-each
    ( lambda( obj )
        ( select-object! obj )
    )
    objs
    )

) ; on_paste()

( add-hook! paste-objects-hook on_paste )

;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

Place the code in ${HOME}/.gEDA/gschemrc file.
Tested on latest git version of geda-gaf.


> In 1.8.2, a window selection of multiple objects can select individual
> attributes of a component, rather than the earlier, more logical
> all-or-nothing rule. This breaks the inviolability of a component object,
> and makes it too easy to inadvertently break components and create
> unattached attributes.

Could you elaborate, please, on how exactly multiple
attributes/objects/components
selection algorithm should look like?

Dmitry.