highlight collisions incorrectly snaps endpoint to collision boundary

Bug #1707105 reported by hauptmech
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
KiCad
Fix Released
Unknown

Bug Description

When using GAL highlight collision mode, the trace endpoint is snapped to the yellow octogon pad collision boundary rather than staying with the cursor. This makes fine manual placement difficult.

Revision history for this message
Tomasz Wlostowski (twlostow) wrote :

Someone before you complained that staying with the cursor is the wrong way and demanded snapping to the clearance area...

Changed in kicad:
importance: Undecided → Wishlist
Revision history for this message
hauptmech (hauptmech) wrote : Re: [Bug 1707105] [NEW] highlight collisions incorrectly snaps endpoint to collision boundary

Cool. Though I'd expect snapping to the valid clearance distance rather
than snapping to a invalid configuration is what that type of user would
want.

Presumably they gave you feedback that the new behaviour was what they
wanted. Can you link in that info here?

Meanwhile I'm laying out with ignore collision turned on and working around
this by laying the track outside of snap distance and the dragging the
track into position.

If snapping is the correct behaviour for some users then I request a
preferences setting even if the snapping to an invalid configuration
reported here is a bug.

On Saturday, July 29, 2017, Tomasz Wlostowski <email address hidden>
wrote:
> Someone before you complained that staying with the cursor is the wrong
> way and demanded snapping to the clearance area...
>
>
> ** Changed in: kicad
> Importance: Undecided => Wishlist
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1707105
>
> Title:
> highlight collisions incorrectly snaps endpoint to collision boundary
>
> Status in KiCad:
> New
>
> Bug description:
> When using GAL highlight collision mode, the trace endpoint is snapped
> to the yellow octogon pad collision boundary rather than staying with
> the cursor. This makes fine manual placement difficult.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/kicad/+bug/1707105/+subscriptions
>

Revision history for this message
KiCad Janitor (kicad-janitor) wrote :

KiCad bug tracker has moved to Gitlab. This report is now available here: https://gitlab.com/kicad/code/kicad/-/issues/2070

Changed in kicad:
status: New → Expired
Changed in kicad:
importance: Wishlist → Unknown
status: Expired → 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.