kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #35185
Re: [PATCH] Fix for bug/1754049
Le 26/03/2018 à 01:31, Wayne Stambaugh a écrit :
> Now that a fix for the lost data has been merged, we should defer the fix for how to handle deleting
> objects from removed layers until v6. In the mean time, we should clearly define the behavior
> before we write any code to prevent any wasted developer time.
>
> Cheers,
>
> Wayne
Hi Wayne,
Before waiting for V6, there are a few things that must be fixed.
- Minor issues:
* I am thinking the layers now used in DRC should be not removable (edge cut, courtyards and in the
future margin layer)
I have a basic fix for that.
* non copper layers used in footprints can be removed (without fortunately destroying the
footprint) without warning: I have a fix to warn the user then removed non copper layers are in use
in a footprint.
-Not so minor issues:
Multilayers items (blind/buried vias, keepout zones) are incorrectly handled:
* In GAL mode, removed Multilayers items are still visible after deletion.
* In all modes: because undo is not handled, if a removed item (for instance a track) was previously
modified (and therefore in the undo list), and if a undo command is made, Pcbnew crashes.
At least the undo/redo list should be cleared.
--
Jean-Pierre CHARRAS
Follow ups
References
-
[PATCH] Fix for bug/1754049
From: hauptmech, 2018-03-14
-
Re: [PATCH] Fix for bug/1754049
From: Seth Hillbrand, 2018-03-14
-
Re: [PATCH] Fix for bug/1754049
From: hauptmech, 2018-03-18
-
Re: [PATCH] Fix for bug/1754049
From: Seth Hillbrand, 2018-03-19
-
Re: [PATCH] Fix for bug/1754049
From: Eeli Kaikkonen, 2018-03-20
-
Re: [PATCH] Fix for bug/1754049
From: Wayne Stambaugh, 2018-03-21
-
Re: [PATCH] Fix for bug/1754049
From: jp charras, 2018-03-22
-
Re: [PATCH] Fix for bug/1754049
From: Andrey Kuznetsov, 2018-03-22
-
Re: [PATCH] Fix for bug/1754049
From: jp charras, 2018-03-22
-
Re: [PATCH] Fix for bug/1754049
From: hauptmech, 2018-03-22
-
Re: [PATCH] Fix for bug/1754049
From: Wayne Stambaugh, 2018-03-25