Legacy Toolset default in Footprint Editor

Bug #1811982 reported by Piotr Gałka
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
KiCad
Fix Released
Low
Jeff Young

Bug Description

I have reported a Bug #1811821 being not avare that I am working in Legacy Toolset (F9). When I got that knowledge I have written there how r12136 behaved in that subject (probably not important now).

I have installed todays Windows 64 nightly (r12157). Now it is better but still F9 is default if not run PcbNew.
Is better because I didn't noticed automatic change to F9 after once set F11 what had place in r12136.

Step by step:
1. delete Roaming/kicad dir,
2. run KiCad
3. open pic_programmer.pro (a copy in my working dir) as without it nothing works.
4. run Footprint Editor
5. Look into settings - I am in F9

You are working in Footprint Editor in F9 till you first run PcbNew.

I am at stage of preparing my libraries so didn't run PcbNew. I was sure that since 5.0.0 default is Modern Toolset so didn't checked it.

Application: kicad
Version: (6.0.0-rc1-dev-1542-gf9f87b3ff), 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'll set this low as running pcbnew once will resolve this unless there are knock-on effects.

Changed in kicad:
importance: Undecided → Low
status: New → Triaged
Jeff Young (jeyjey)
Changed in kicad:
assignee: nobody → Jeff Young (jeyjey)
milestone: none → 5.1.0
Jeff Young (jeyjey)
Changed in kicad:
status: Triaged → In Progress
Revision history for this message
Seth Hillbrand (sethh) wrote :

Hi Jeff-

After this change, eeschema no longer saves the fallback state. If I edit the config file to be canvas_type=2, I can get cairo to start on open. But if I select OpenGL (when not supported), I get the message saying "Could not use OpenGL, falling back to software rendering". But it saves canvas_type=1 and gives me the same message again on starting next time. Apart from editing the config file, I can no longer get it to save Cairo as my default.

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

Fixed in revision 7bec707160d4834b141a908ac3e18c619b4829a7
https://git.launchpad.net/kicad/patch/?id=7bec707160d4834b141a908ac3e18c619b4829a7

Changed in kicad:
status: In Progress → Fix Committed
Revision history for this message
Jeff Young (jeyjey) wrote :

@Seth, was the Kicad Janitor 5 hours late, or was your message referring to an earlier change?

If it was referring to 7bec707160d4834b141a908ac3e18c619b4829a7, that would be a pretty good trick as I only changed footprint_edit_frame.cpp and pcb_edit_frame.cpp. (Not that I haven't managed pretty good tricks before.)

JP did make some changes here earlier. Perhaps that's what sunk eeschema?

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

Sorry Jeff, I got my bisect wrong. Thanks for the headsup

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.