Next wx release?

[Mark Roszko]

Are there any plans for a wx 3.3.2 release soon? It's been 6 months since 3.3.1

We are looking at a kicad major release soon and it would be nice to have a updated tagged release of wx for dark mode fixes.

[Vadim Zeitlin]

On Fri, 23 Jan 2026 10:06:50 -0800 (PST) Mark Roszko wrote:

MR> Are there any plans for a wx 3.3.2 release soon? It's been 6 months since
MR> 3.3.1

Yes, I do hope to make it soon, but there are still a few things that I'd
like to fix first, notably a couple of bugs reported by KiCad people
(#26106 concerning wrongly deleting HBITMAPs in wxMSW with wxStaticBitmap
and #24558 to disable IME when editing wxGrid reported by you) and it would
be nice to apply the changes in #26053 which improves dark mode support
too.

MR> We are looking at a kicad major release soon and it would be nice to have a
MR> updated tagged release of wx for dark mode fixes.

What is your schedule like? I definitely need to fix #26106 but I hope to
do it this weekend. I think #24558 can be postponed, but #26053 would
definitely be nice to have in 3.3.2 if we have time to do it.

Unrelatedly, there are some macOS 26 fixes/improvements which it would be
good to have in this release too but I'm not sure I dare to do anything
there without Stefan's input or at least approval, so this doesn't depend
on me.

Anyhow, please let me know when is KiCad release planned and we'll see
what can be done.

Thanks,
VZ

--
TT-Solutions: wxWidgets consultancy and technical support
https://www.tt-solutions.com/

[Mark Roszko]

Currently we are looking to start to create a few release candidates soon with a final release by the end of February. It's a little tentative as we are behind schedule with polishing and cramming in last minute features so that may get pushed out a little.

We are currently keeping macOS on 3.2 with just backports of bug fixes. We have a wxpython dependency and I've only patched it out Windows build with 3.3.

Thanks,

Mark

[Vadim Zeitlin]

On Fri, 23 Jan 2026 13:52:41 -0500 Mark Roszko wrote:

MR> Currently we are looking to start to create a few release candidates soon
MR> with a final release by the end of February.

There is also a question of whether you could use the current master for
these RCs, so that it would get some testing before making 3.3.2 or if you
need 3.3.2 to happen first in order to be able to use it?

As of right now, I think I have the fix for wxStaticBitmap bug (see
https://github.com/wxWidgets/wxWidgets/pull/26110) and I hope the OP
updates the dark fixes PR soon but, failing that, I'll do it myself
(this is https://github.com/wxWidgets/wxWidgets/pull/26053). So another
question is how important would it be to fix IME issues in wxGrid
(https://github.com/wxWidgets/wxWidgets/issues/24558) for you?

Other than that I don't see anything critical preventing us from making
the release soon. If you can make your RCs using current master (we could
tag it as 3.3.2-rcN too, if it would help), then we could make the release
slightly later, but if not, we could do it in the beginning of February, I
think (February 2 would conform to our usual conventions).

MR> We are currently keeping macOS on 3.2 with just backports of bug fixes.

If we decide to make 3.3.2 very soon, I think we'd better postpone with
applying Robert's PRs until after it as they almost certainly won't get
enough testing before the release.

MR> We have a wxpython dependency and I've only patched it out Windows
MR> build with 3.3.

I'd be curious to know how did you build wxPython with 3.3 as I ran into
many errors while trying to do it (see https://github.com/wxWidgets/Phoenix/issues/2845).

[Danny Scott]

After Feb 3 works for me.

Danny

[Mark Roszko]

I maintain our own build setup for wxpython using cmake instead of the upstream python nonsense.

https://gitlab.com/kicad/packaging/kicad-vcpkg-registry/-/tree/main/ports/wxpython-33?ref_type=heads

The two patch files located at the above url will allow building with wx 3.3.

It's not a perfect patch as I lazily disabled some parts of wx but nobody uses it generally in our case and I have finite time to deal with it.

[Vadim Zeitlin]

On Sat, 24 Jan 2026 23:03:35 -0500 Mark Roszko wrote:

MR> I maintain our own build setup for wxpython using cmake instead of the
MR> upstream python nonsense.
MR>
MR> https://gitlab.com/kicad/packaging/kicad-vcpkg-registry/-/tree/main/ports/wxpython-33?ref_type=heads
MR>
MR> The two patch files located at the above url will allow building with wx
MR> 3.3.

Thanks! I've mentioned them in https://github.com/wxWidgets/Phoenix/issues/2845
as they should probably be applied to 3.3 branch of wxPython itself, at
least partially.

Also, sorry to insist, but I'd like to return to this question:

MR> On Sat, Jan 24, 2026, 2:40 PM Vadim Zeitlin <va...@wxwidgets.org> wrote:
[...]
MR> > There is also a question of whether you could use the current master for
MR> > these RCs, so that it would get some testing before making 3.3.2 or if you
MR> > need 3.3.2 to happen first in order to be able to use it?

as 3.3.2 planning would be quite different depending on the answer. After
going through the recent issues, I've realized there there were more things
that it would be good-to-great to fix before 3.3.2 (most of them reported
as affecting KiCad), see the updated list:

https://github.com/wxWidgets/wxWidgets/issues?q=is%3Aopen%20milestone%3A%223.3.2%22

We almost surely won't have the time to do all this, and the ones that
should be prioritized depend on the date of the release.

Right now my window is from February 3rd to March 3rd. I'd only do it at
the earliest date if you absolutely need a release before making your RCs,
so please let me know if you do.

Thanks!

[Mark Roszko]

FYI, I moved KiCad to a updated wx master build. The only annoying part is that it is reporting wx 3.3.2 as the version string early but that's minor.

[Vadim Zeitlin]

On Wed, 28 Jan 2026 09:15:41 -0500 Mark Roszko wrote:

MR> FYI, I moved KiCad to a updated wx master build.

So does this mean that we have time to fix more things in master and make
the final 3.3.2 on March 3rd, for example?

MR> The only annoying part is that it is reporting wx 3.3.2 as the version
MR> string early but that's minor.

This is intentional to allow using stuff in current master which were not
in 3.3.1 by guarding them with wxCHECK_VERSION(3,3,2) check. However we
could easily add some wxVERSION_STATUS which could be set to "dev", "rcN"
or "release". Please let me know and/or open an issue if something like
this could be useful.

Thanks,

[Mark Roszko]

> So does this mean that we have time to fix more things in master and make
the final 3.3.2 on March 3rd, for example?

Yes, we can even release KiCad like this. I can apply any more urgent patches on top.