KISYS3DMOD path variable apparently hard coded
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
KiCad |
Fix Released
|
Medium
|
Wayne Stambaugh |
Bug Description
In the latest Windows nightly, Version: (6.0.0-
Moreover, in most cases Kicad get stuck on this dialog with high CPU activity, and I need to let Windows terminate KiCad. Even if I press Cancel in the Configure path Window I get this dialog, and get stuck. I have in a couple of cases I was able to get past the dialog, and next time KiCad was started the path was reset to the program folder.
If it is intentional that this variable is locked to the program folder I disagree, and it will create problems for all custom footprint libraries that had to use the KYSYS3D model variable as root for their 3D model location. It will also prevent official libraries to be installed anywhere but the program folder, so users will need administrative privileges to make any updates beyond the KiCad install.
This might be related to the following commit: https:/
(I am not sure what this implies, perhaps it refers to the stuck dialog?) It works fairly well under 5.0 rc3 so I am not sure why it was changed.
Application: kicad
Version: (6.0.0-
Libraries:
wxWidgets 3.0.3
libcurl/7.54.1 OpenSSL/1.0.2l zlib/1.2.11 libssh2/1.8.0 nghttp2/1.23.1 librtmp/2.3
Platform: Windows 7 (build 7601, Service Pack 1), 64-bit edition, 64 bit, Little endian, wxMSW
Build Info:
wxWidgets: 3.0.3 (wchar_t,wx containers,
Boost: 1.60.0
OpenCASCADE Community Edition: 6.8.0
Curl: 7.54.1
Compiler: GCC 7.1.0 with C++ ABI 1011
Build settings:
USE_
USE_
KICAD_
KICAD_
KICAD_
KICAD_
BUILD_
KICAD_
KICAD_
KICAD_SPICE=ON
Changed in kicad: | |
milestone: | none → 5.1.0 |
Changed in kicad: | |
status: | New → Triaged |
importance: | Undecided → Medium |
assignee: | nobody → Wayne Stambaugh (stambaughw) |
Changed in kicad: | |
status: | Fix Committed → Fix Released |
Also happens on linux, no high cpu usage though