Hello!
On 2016-05-09 17:50, Chris Pavlina wrote:
> If they are "locked", then yes, I think they should not be moved, neither by
> the user nor by PNS.
You might consider that we might need *different* levels of locking /
protections
for traces, manually vs. pns/automatically routed, trace widths
If they are "locked", then yes, I think they should not be moved, neither by
the user nor by PNS.
On Mon, May 09, 2016 at 05:43:24PM +0200, Maciej Sumiński wrote:
> I have noticed there is an option to mark tracks & vias as 'locked' in
> the legacy canvas (right click on a track->Set Flags->Track:
Yes! This should have been done on the legacy canvas as well. When I
lock an object, I don't want it to be changed in any way unless I
explicitly unlock it. This concept seems pretty straight forward to me.
I believe there are few bug reports against legacy canvas on this.
On 5/9/2016 11:43 AM
I have noticed there is an option to mark tracks & vias as 'locked' in
the legacy canvas (right click on a track->Set Flags->Track: Locked.
According to my observations, it is only used by Global Deletion dialog.
Should we make locked tracks & vias behave like locked modules, so they
cannot be mov
4 matches
Mail list logo
