wxGrid::UseNativeColHeader( true ) results in blank column labels when wxGrid is wider than window.
Potentially MacOS-only.
Ref KiCad bug: https://gitlab.com/kicad/code/kicad/-/issues/18198
Add the line:
grid->UseNativeColHeader( true );
after:
grid->CreateGrid( 0, 0 );
in griddemo.cpp. (Should be around line 598.)
Build the sample.
Scroll the grid to the left. Note that newly-exposed columns on the right have blank column headers.
Application: KiCad Schematic Editor arm64 on arm64
Version: 9.99.0-4297-gf7d04c29ea-dirty, debug build
Libraries:
wxWidgets 3.2.8
FreeType 2.13.3
HarfBuzz 11.0.1
FontConfig 2.14.0
libcurl/8.7.1 (SecureTransport) LibreSSL/3.3.6 zlib/1.2.12 nghttp2/1.61.0
Platform: macOS Sonoma Version 14.6.1 (Build 23G93), 64 bit, Little endian, wxMac
OpenGL: Apple, Apple M1 Max, 2.1 Metal - 88.1
Build Info:
Date: Dec 6 2025 13:00:29
wxWidgets: 3.2.8 (wchar_t,wx containers)
Boost: 1.88.0
OCC: 7.9.0
Curl: 8.7.1
ngspice: 44.2
Compiler: Clang 16.0.0 with C++ ABI 1002
Build settings:
KICAD_IPC_API=ON
KICAD_USE_PCH=OFF
KICAD_STDLIB_DEBUG=OFF
KICAD_STDLIB_LIGHT_DEBUG=OFF
KICAD_SANITIZE_ADDRESS=OFF
KICAD_SANITIZE_THREADS=OFF
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
Unfortunately this is indeed Mac-specific, this diff
diff --git a/samples/grid/griddemo.cpp b/samples/grid/griddemo.cpp index a93defedf0..0ee5f63421 100644 --- a/samples/grid/griddemo.cpp +++ b/samples/grid/griddemo.cpp @@ -619,6 +619,7 @@ GridFrame::GridFrame() // this will create a grid and, by default, an associated grid // table for strings grid->CreateGrid( 0, 0 ); + grid->UseNativeColHeader( true ); grid->GetTable()->SetAttrProvider(new CustomColumnHeadersProvider());
reproduces the problem for me there but not under Windows or Linux (where this exposed another small problem which I fixed, but not this one).
Will try to debug, but as usual with Mac stuff I'm not exactly brimming with confidence...
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
Well, I have a fix, see #26016, but, as I suspected I wasn't able to fix the underlying bug in wxOSX, so this fix is just a workaround — but I don't think there are any drawbacks to doing it like this.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
Closed #26014 as completed via 411430b.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()