| 2017-01-13 09:48:09 |
ikletti |
description |
Changing the color of footprint pads on the "Render" tab in Pcbnew is immediate when the default canvas is active.
In the OpenGL and the Cairo canvas, the change does not happen until another canvas is activated or the OpenGL or Cairo canvas is reloaded (i.e. pressing the F11 or F12 button). Using redraw (F3 button) does not initiate the color change.
This was first noticed on a Debian 8 / Kicad 4.0.2 production system. Version information:
Application: kicad
Version: 4.0.2+dfsg1-2~bpo8+1-stable release build
wxWidgets: Version 3.0.2 (debug,wchar_t,compiler with C++ ABI 1002,GCC 4.9.2,wx containers,compatible with 2.8)
Platform: Linux 3.16.0-4-686-pae i686, 32 bit, Little endian, wxGTK
Boost version: 1.55.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=OFF
The same behavior is present in the Nightly build 2017-01-09 revision c2fb336 on a Windows 7 test installation.
Version information:
Application: kicad
Version: (2017-01-09 revision c2fb336)-makepkg, release build
Libraries: wxWidgets 3.0.2
libcurl/7.46.0 OpenSSL/1.0.2d zlib/1.2.8 libidn/1.32 libssh2/1.6.0 librtmp/2.3
Platform: Windows 7 (build 7601, Service Pack 1), 32 bit, Little endian, wxMSW
- Build Info -
wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8)
Boost: 1.59.0
Curl: 7.46.0
KiCad - Compiler: GCC 5.2.0 with C++ ABI 1009
Settings: USE_WX_GRAPHICS_CONTEXT=OFF
USE_WX_OVERLAY=OFF
KICAD_SCRIPTING=ON
KICAD_SCRIPTING_MODULES=ON
KICAD_SCRIPTING_WXPYTHON=ON
BUILD_GITHUB_PLUGIN=ON
KICAD_USE_SCH_IO_MANAGER=OFF
KICAD_USE_OCE=ON
|
Changing the color of footprint pads on the "Render" tab in Pcbnew is immediate when the default canvas is active.
In the OpenGL and the Cairo canvas, the change does not happen until another canvas is activated or the OpenGL or Cairo canvas is reloaded (i.e. pressing the F11 or F12 button). Using redraw (F3 button) does not initiate the color change.
This was first noticed on a Debian 8 / Kicad 4.0.2 production system.
Version information:
Application: kicad
Version: 4.0.2+dfsg1-2~bpo8+1-stable release build
wxWidgets: Version 3.0.2 (debug,wchar_t,compiler with C++ ABI 1002,GCC 4.9.2,wx containers,compatible with 2.8)
Platform: Linux 3.16.0-4-686-pae i686, 32 bit, Little endian, wxGTK
Boost version: 1.55.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=OFF
The same behavior is present in the Nightly build 2017-01-09 revision c2fb336 on a Windows 7 test installation.
Version information:
Application: kicad
Version: (2017-01-09 revision c2fb336)-makepkg, release build
Libraries: wxWidgets 3.0.2
libcurl/7.46.0 OpenSSL/1.0.2d zlib/1.2.8 libidn/1.32 libssh2/1.6.0 librtmp/2.3
Platform: Windows 7 (build 7601, Service Pack 1), 32 bit, Little endian, wxMSW
- Build Info -
wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8)
Boost: 1.59.0
Curl: 7.46.0
KiCad - Compiler: GCC 5.2.0 with C++ ABI 1009
Settings: USE_WX_GRAPHICS_CONTEXT=OFF
USE_WX_OVERLAY=OFF
KICAD_SCRIPTING=ON
KICAD_SCRIPTING_MODULES=ON
KICAD_SCRIPTING_WXPYTHON=ON
BUILD_GITHUB_PLUGIN=ON
KICAD_USE_SCH_IO_MANAGER=OFF
KICAD_USE_OCE=ON |
|
