lock items in cairo

Bug #1551562 reported by Nicholas Savenlid
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
KiCad
Fix Released
Wishlist
Unassigned

Bug Description

Hi,

Cant lock items in pcbnew cairo canvas

need to toogle back and forth between canvas

maybe this is supposed to be lika this because of some unknown legacy backgrund unknown to me.

cairo looks way better and performs drags much better thats why i use it.

thanks again for all your work.

Related branches

Revision history for this message
Maciej Suminski (orsonmmz) wrote :

Hi Nicholas,

You should be able to lock footprints either by selecting a footprint and pressing 'L' or with the Properties window. I assume the report is about a missing entry in the right click context menu?

tags: added: missing-gal-tool
Revision history for this message
Nicholas Savenlid (nicholas-z) wrote : Re: [Bug 1551562] Re: lock items in cairo

I want to lock vias and traces.
Den 1 mar 2016 16:11 skrev "Maciej Sumiński" <email address hidden>:

> Hi Nicholas,
>
> You should be able to lock footprints either by selecting a footprint
> and pressing 'L' or with the Properties window. I assume the report is
> about a missing entry in the right click context menu?
>
> ** Tags added: missing-gal-tool
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1551562
>
> Title:
> lock items in cairo
>
> Status in KiCad:
> New
>
> Bug description:
> Hi,
>
> Cant lock items in pcbnew cairo canvas
>
> need to toogle back and forth between canvas
>
> maybe this is supposed to be lika this because of some unknown legacy
> backgrund unknown to me.
>
> cairo looks way better and performs drags much better thats why i use
> it.
>
> thanks again for all your work.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/kicad/+bug/1551562/+subscriptions
>

Revision history for this message
Nicholas Savenlid (nicholas-z) wrote :

Hi

Yes but i mean lock vias and traces

any object alike

i can lock in legacy but it wont stay locked once switched back to cairo

Revision history for this message
Maciej Suminski (orsonmmz) wrote :

What makes you say it is not locked anymore? If I lock a track in legacy canvas, then switch to Cairo and back - it stays locked.
Please tell us which KiCad revision do you use.

Revision history for this message
Nicholas Savenlid (nicholas-z) wrote :

I use 2016-01-17 BZR 6562 git 78d0cfc
wxwidgets 3.0.2
unicode etc 1.57.0

I only locked a via, i did not try to lock a trace, but the via moved in cairo

switching back to legacy confirmed it was still locked

i will check again.

thanks

/Nicholas

Revision history for this message
Nicholas Savenlid (nicholas-z) wrote :

I tried again

locked traces and / or vias move around freely iif i drag a nearby object in cairo.

Revision history for this message
martin layley (martin-scoutingsquirrel) wrote :

No lock facility at all for pads & traces in OpenGL on OSX. Only for footprints

Revision history for this message
Novak Tamas (novak-7) wrote :

No locking for vias and traces even in Windows. I can't see what it would be used for. Maybe antenna or touch sensor patterns? They may be created and placed as footprint.
File to wishlist, Nicholas, if you still need this feature.

Changed in kicad:
status: New → Invalid
importance: Undecided → Wishlist
Revision history for this message
Chris Pavlina (pavlina-chris) wrote :

Novak, stop setting bugs "invalid" and saying they're "filed to wishlist". Nobody looks at the invalid bug reports, they're "closed". You're essentially tossing them in the bin and telling the reporter you're not. I specifically filter out Invalid reports when browsing the tracker as most of them are accidental reports and the like that nobody needs to look at.

Changed in kicad:
status: Invalid → Opinion
status: Opinion → Confirmed
Revision history for this message
Novak Tamas (novak-7) wrote :

Hello Chris,
sorry for the mess:)) My scheme was that
if I set Importance to Wishlist, it is not New any more, so Status should be set
to another value. As we are hunting for bugs, if something is not bug (but a wish)
then it is an invalid bugreport.
Now I see your point: invalid will be neglected, so further on I set Importance=Wishlist cases
to Status=Triaged.
(although you simply have left Status=New, after setting Importance to Wishlist
like at https://bugs.launchpad.net/kicad/+bug/1534386 . Is this better practice let it be New?)

Some revolutionary ideas:)

- lots of folks here are not native English speakers. I also had to look up the dictionary
what "triaged" meant. A "handled", "managed", or "decided" would be easier for us
"I english no good" guys:))

- The "Wishlist" should be an member of Status, not Importance. If Wishlist goes to Status,
wishlisted items may receive different (sometimes distinguished) importance. I think there
are wishlist items which are much more important than rare-to-face bugs.

Some of them are --in my opinion-- very easy to do. E.g.:
https://bugs.launchpad.net/kicad/+bug/1560840
https://bugs.launchpad.net/kicad/+bug/1530543

Some of them are very important for productivity. E.g. I always use copying blocks
from my older designs to new one. It would be easy by opening two pcb_new's or eeschema's,
load two different boards/schemas, and Ctrl+C, Ctrl+V the blocks between them.
Like https://bugs.launchpad.net/kicad/+bug/594086

If bugreport forum is on an e.g. MySQL database, all records could be set to new system
by simple database console commands: all (Status=* and Importance=Wishlist) are replaced
with Status=Wishlist and Importance=Low. Importance may be set higher later. I don't know if
web programming is easy to alter, but I think it was worth.

cheers,
Tamás

2016. április 17., 21:10:23, írtad:

> Novak, stop setting bugs "invalid" and saying they're "filed to
> wishlist". Nobody looks at the invalid bug reports, they're "closed".
> You're essentially tossing them in the bin and telling the reporter
> you're not. I specifically filter out Invalid reports when browsing the
> tracker as most of them are accidental reports and the like that nobody
> needs to look at.

> ** Changed in: kicad
> Status: Invalid => Opinion

> ** Changed in: kicad
> Status: Opinion => Confirmed

                           mailto:<email address hidden>

Revision history for this message
Maciej Suminski (orsonmmz) wrote :

I have just added 'Locking' menu to GAL context menu, but it works in a different way than module locking (but in the same way as in the legacy canvas). It only influences the list of tracks to be deleted using 'Global Deletion' dialog. I am going to discuss the current approach on the developer mailing list.

Revision history for this message
Maciej Suminski (orsonmmz) wrote :

In the current revision once tracks/vias are locked they require permission to be moved. If I understood correctly the request, now the report can be closed. I set this to 'Incomplete' and look forward to your feedback.

Changed in kicad:
status: Confirmed → Incomplete
status: Incomplete → Fix Committed
Revision history for this message
Maciej Suminski (orsonmmz) wrote :

s/Incomplete/Fix Committed/

Revision history for this message
Nicholas Savenlid (nicholas-z) wrote :

Thanks.

I am not in layout phase right now so cant comment.

probably will take a month or 2 before next design, as i am in software phase now dealing with earler hw designs.

i do work a lot with kicad but not exactly now.

thanks
/Nicholas

Changed in kicad:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.