Footprint Editor - selected layer not at front

Bug #1811821 reported by Piotr Gałka
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
KiCad
Fix Released
Low
Seth Hillbrand

Bug Description

In few days old version in Footprint Editor even if I select F.SilkS as active layer I always see F.CrtYd in front of it.

Application: kicad
Version: (6.0.0-rc1-dev-1521-g81a0ab4d7), release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.61.1 OpenSSL/1.1.1 (WinSSL) zlib/1.2.11 brotli/1.0.6 libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.5) nghttp2/1.34.0
Platform: Windows 7 (build 7601, Service Pack 1), 64-bit edition, 64 bit, Little endian, wxMSW
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.68.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.61.1
    Compiler: GCC 8.2.0 with C++ ABI 1013

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=OFF
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON

Revision history for this message
Seth Hillbrand (sethh) wrote :

I am unable to confirm this on Linux. Can you post a screencapture or image showing the effect and including the layers manager window

Changed in kicad:
status: New → Incomplete
Revision history for this message
Wayne Stambaugh (stambaughw) wrote :

I'm not seeing this issue as you can see in the screen capture. Both courtyard layers are behind the currently selected front silkscreen layer.

Application: kicad
Version: (6.0.0-rc1-dev-1538-g72c885797-dirty), release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.63.0 OpenSSL/1.1.1a (WinSSL) zlib/1.2.11 brotli/1.0.7 libidn2/2.1.0 libpsl/0.20.2 (+libidn2/2.1.0) nghttp2/1.35.1
Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian, wxMSW
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.69.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.63.0
    Compiler: GCC 7.4.0 with C++ ABI 1011

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=OFF
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON

Revision history for this message
jean-pierre charras (jp-charras) wrote :

In fact, I am seeing F.Fab always on top on F.Silks, even if F.Silks and not F.CrtYd

Revision history for this message
Piotr Gałka (piotrgalka) wrote :

In my footprints I drow the same lines at SilkS and at CrtYd. And I see the same colour line no matter if I have selected CtrYd or Silk.
To standard 0603 resistor I'he added a cross. Even if F.SilkS is selected the F.CrtYd is on top. But now, as I have cross and not one line on another I see that F.CrtYd is a little transparent. I was not sure if not an optic mirage so I have checked.
CrtYd line is RGB: 194/194/194
In cross section RGB: 194/198/198

Revision history for this message
Seth Hillbrand (sethh) wrote :

OK, I can see this now. It only occurs in fallback canvas. I see F.Crtyd and F.Fab in front of F.Silk

Changed in kicad:
milestone: none → 5.1.0
status: Incomplete → Triaged
Revision history for this message
Piotr Gałka (piotrgalka) wrote :

I was not aware I am working in F9 (I was sure that in F11, but didn't checked it). I didn't noticed when I have switched to F9 (certainly it was no my intention anytime). And it was at two PCs I have installed r12136. To check now if it is not default I deleted the AppData/Roaming/kicad and run KiCad and it asks if I wont a graphic acceleration and I accept it and after it I work with F11 active.
At one PC I am working so may be by inattention I pressed F9, but at second I only run it to see the KiCad libraries and to see the menus in English. Nothing more - no chance to press F9.

I don't care how KiCad works in F9. I care why I was in F9 at two PCs being not aware of it.

May be this language....

I have opened KiCad once more, changed language and.... I am in F9. I didn't checked what was the state before changing language so at that moment not sure if second running of KiCad or changing Language.

So once more step by step:
1. delete Roaming/kicad dir,
2. run KiCad
3. open pic_programmer.pro (copy in my working dir) as without it nothing works
4. run Footprint Editor
5. Look into settings - I am in F9 - Surprice !!!
I realised 1..5 once more with the same effect.

After makeing many other step by steps I decided that the idea that changing language is the source is the wrong track.

So a different step by step:
1.
2.
3.
4. Run PcbNew and accept graphic acceleration - I am in F11
5. Close PcbNew
6. Run Footprint Editor - I am in F11
7. Close Footprint Editor
8. Run PcbNew - I am in F9 !!!!

One more - this time only PcbNew - in third opening get into F9:
1.
2.
3.
4. Run PcbNew and accept graphic acceleration - I am in F11
5. Close PcbNew
6. Run PcbNew - I am in F11
7. Close PcbNew
8. Run PcbNew - I am in F9 !!!!

So it is not the Footprint Editor. If it would be at second opening it would look more probable but at third opening - what is the difference betwean second and third.

I will check with todays nightly and if still it works that way I'll copy this my post as new bug report.

Changed in kicad:
importance: Undecided → Low
Revision history for this message
KiCad Janitor (kicad-janitor) wrote :

Fixed in revision 08c944a46792e7365c823c3e8a8f08b98d7cf628
https://git.launchpad.net/kicad/patch/?id=08c944a46792e7365c823c3e8a8f08b98d7cf628

Changed in kicad:
status: Triaged → Fix Committed
assignee: nobody → Seth Hillbrand (sethh)
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.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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