Pad clearance not visible with OpenGL

Bug #1570832 reported by Robin Whittle
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
KiCad
Confirmed
Low
Unassigned

Bug Description

I haven't tried this with the latest nightly, because the machine I have to test that doesn't do OpenGL, due to it being a VM under VirtualBox. So this report is about version 4.0.2:

Application: pcbnew
Version: 4.0.2-stable release build
wxWidgets: Version 3.0.2 (debug,wchar_t,compiler with C++ ABI 1009,GCC 5.2.0,wx containers,compatible with 2.8)
Platform: Windows 7 (build 7601, Service Pack 1), 64-bit edition, 64 bit, Little endian, wxMSW
Boost version: 1.57.0
         USE_WX_GRAPHICS_CONTEXT=OFF
         USE_WX_OVERLAY=OFF
         KICAD_SCRIPTING=ON
         KICAD_SCRIPTING_MODULES=ON
         KICAD_SCRIPTING_WXPYTHON=ON
         USE_FP_LIB_TABLE=HARD_CODED_ON
         BUILD_GITHUB_PLUGIN=ON

With the default canvas I can see a line around pads when I turn on: Preferences > Display > Show pad clearance.

No such things are visible when I do this with the OpenGL canvas or the Cairo canvas (which is very slow).

The closest potentially related bug report I could find is from 2014: https://bugs.launchpad.net/kicad/+bug/1333100 .
See also a report I just made "Solder mask layer not visible with default canvas": https://bugs.launchpad.net/kicad/+bug/1570831 .

Thanks for KiCad!

Tags: cern gal pcbnew
tags: added: cern gal
removed: opengl
Revision history for this message
Novak Tamas (novak-7) wrote :

It is a similar feature to turn on Preferences - Interactive routing - Mode=Highlite collisions. You see green light when in proximity.
On the other hand if you select "Shove" the clearance will be maintained automatically, no really need to show clearance.

Changed in kicad:
status: New → Confirmed
Novak Tamas (novak-7)
Changed in kicad:
importance: Undecided → Low
Revision history for this message
Rogier Lodewijks (rogier-f) wrote :

Possibly a bit of topic, but IMO the collision highlighting would be of great help when searching/fixing DRC violations. Currently the DRC markers only point you in the general direction of the error. It's up to the user to find out what's wrong exactly. Personally I think the DRC-error highlighting in Eagle is very nice, clearly pointing out the issue. (example: http://i.stack.imgur.com/3ni9Q.png)

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

@Rogier I agree. I'd rephrase the wish as not pad clearance should be visible everywhere, but DRC error display should be enhanced with showing clearance area borders, and hilite their collisions.

Revision history for this message
Strntydog (strntydog) wrote :

Clearance is a nice thing to see when laying tacks, even though GAL can highlight collisions, you need to then back track until the collision goes away, the "halo" can help a designer see what the clearance is along his entire track, just because there is no collision DOES NOT mean that clearance is optimal for the track.

http://i.imgur.com/2AzG3cy.png <- Shows clearance for the current track (in legacy)
http://i.imgur.com/BSX7jkc.png <- GAL Doesnt.

It doesn't seem like an unreasonable request for a designer to be able to enable the visible clearance lines to a track they are routing on GAL, and I would really like them.

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.