Hi,
This patch adds a missing tool to GAL: duplicate zone onto layer.
It's accessed through the zones context menu and does the same as the
legacy mode version.
Cheers,
John
From 031b15406695e60b17af6bb9e8b984e662c728d8 Mon Sep 17 00:00:00 2001
From: John Beard
Date: Mon, 6 Feb 2017 11:45:56 +
Hi,
I committed the patch just to remove any potential 'this is not
available in GAL' complaints, but IMHO this particular feature is
needless and clutters the menu.
The code itself is obviously fine, I am just considering the value of
having a dedicated menu entry for such operation, but we can
Just as sidenote, that is the zone feature I use the most :)
Regards
Marcos
On Thu, Feb 9, 2017 at 8:51 AM, Maciej Suminski
wrote:
> Hi,
>
> I committed the patch just to remove any potential 'this is not
> available in GAL' complaints, but IMHO this particular feature is
> needless and clutt
I have never used it and I find the menu in legacy a bit to cluttered.
an alternative might be that when duplicating a layer (Ctrl+D), It would
get duplicated to the chosen layer in the right hand layer menu, as with
tracks.
-Kristoffer
On 2017-02-09 17:10, Marcos Chaparro wrote:
Just as si
What are your use cases? It is likely I am missing something, and I do
not want to make decisions basing only on my preferences.
I agree it is a common thing to have a GND zone on both sides of a
board, so they could be created by drawing one zone and then duplicating
it to the other side. The thi
Why is it an issue having a duplicate zone onto layer menu entry in the
zone context menu? Isn't that the point of context menus? I would
think duplicating a zone onto another layer is well within the context
of commands that can be performed on the current zone. If not in the
zone context menu,
I do not negate the location of the menu entry, which is very
appropriate if we want to keep it. What I am discussing is usefulness of
having a dedicated tool to duplicate a zone to another layer, while it
can be easily done using the Duplicate tool and then changing properties
of the duplicated zo
Any reason why we cannot support both?
On 2/9/2017 1:09 PM, Maciej Suminski wrote:
> I do not negate the location of the menu entry, which is very
> appropriate if we want to keep it. What I am discussing is usefulness of
> having a dedicated tool to duplicate a zone to another layer, while it
> c
Nope, we can have both. The only thing I am arguing against is having
redundant tools and cluttering the menus, but if you say it should stay,
then I am fine with that.
On 02/09/2017 07:15 PM, Wayne Stambaugh wrote:
> Any reason why we cannot support both?
>
> On 2/9/2017 1:09 PM, Maciej Suminski
Hi Orson, Wayne
First, good videos at FOSDEM.
Duplicate zone as in OpenGL canvas or duplicate zone onto layer as in
legacy canvas, deserves its own menu entry.
One of them is enough for me. I use this feature in almost every board.
Sometimes I duplicate the zone into another layer, sometimes
10 matches
Mail list logo
