X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type;
        bh=p5+uP5tRn43GzDR22Z2rO0wmhxzWSRTRpHthsUWqNpE=;
        b=ynZv1gTg3zeyhfVYxbistE3uMzQ/js+q2LlWeZs3J4kYOxrV7OcxTctpskxTkq9Tap
         Dsn3mrA/+maUpQqFcJKGWPLYxVoAlnNMa5339hCtUSbAZyTSjfJaoJTqXxBIbwe6siA+
         jRnwIfsCZgoc1B6v835UoF1qRJ2uwHoonn0ojtbC9yry0aZtuwnB6nt88g4zH0CmRuY5
         EyY+WuPYanndZo3IbvkYS70DduzzXSCQZtoDy19bDh5v90tGjqqIu7fwcVaxyTU69kBj
         HAkwPXJ9FShvAeovlL5L+3yZ3Q16ZWzG01O31NVHLytPvUlpFAlis4MIavuE+98nV/Lz
         pgWA==
MIME-Version: 1.0
Sender: silicon DOT on DOT inspiration AT gmail DOT com
In-Reply-To: <k0d64k$ett$1@dough.gmane.org>
References: <20120813012700 DOT 2106039c AT akka>
	<k0d64k$ett$1 AT dough DOT gmane DOT org>
Date: Wed, 15 Aug 2012 08:01:11 +1000
X-Google-Sender-Auth: eelW0gUwer577Hg6ng29vh5Aw1k
Message-ID: <CAKakQceBd86iGqogQzm4UwsWvtHDVgfRWZ62U=OS1-52qdfWpg@mail.gmail.com>
Subject: Re: [geda-user] silk layer names
From: Stephen Ecob <stephen DOT ecob AT sioi DOT com DOT au>
To: geda-user AT delorie DOT com
Content-Type: text/plain; charset=ISO-8859-1
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 Tue, Aug 14, 2012 at 7:35 PM, Kai-Martin Knaak <kmk AT familieknaak DOT de> wrote:
> See attached an obvious expansion of the patch mentioned above. It makes the
> GUI show the actual name of the currently active silk layer rather than a
> hard coded string "silk".
>
> If both patches are applied, the text of the silk layer button in the GUI
> toggles between "top silk" and "bottom silk" when the view is changed with
> the tab key. This makes it more obvious, which of the two silk layers is
> currently active.

Thank you kaimartin, that is a good idea.
I hope this patch makes it into GIT soon :)