Paul Licameli
2016-06-18 20:14:23 UTC
I see that we sometimes specify a patch of wxWidgets source code as a step
in the build process.
Might we do that for the 2.1.3 release if it is necessary to fix high
priority bugs?
I am concerned for Mac especially. Several high priority bugs were
regressions between 2.1.1 and 2.1.2 that are seemingly the fault of
wxWidgets, not our code.
For one, there is this patch which may fix many problems with tab
navigation:
http://trac.wxwidgets.org/attachment/ticket/17341/tab_navigation_fix_general.patch
For another there is this bug:
http://bugzilla.audacityteam.org/show_bug.cgi?id=1338
I don't know yet what might patch it, but I have cloned the wxWidgets git
repository and I am bisecting that. I know things went wrong somewhere
between 3.0.0 and 3.0.1. I might even discover a bug fix for wxWidgets.
PRL
in the build process.
Might we do that for the 2.1.3 release if it is necessary to fix high
priority bugs?
I am concerned for Mac especially. Several high priority bugs were
regressions between 2.1.1 and 2.1.2 that are seemingly the fault of
wxWidgets, not our code.
For one, there is this patch which may fix many problems with tab
navigation:
http://trac.wxwidgets.org/attachment/ticket/17341/tab_navigation_fix_general.patch
For another there is this bug:
http://bugzilla.audacityteam.org/show_bug.cgi?id=1338
I don't know yet what might patch it, but I have cloned the wxWidgets git
repository and I am bisecting that. I know things went wrong somewhere
between 3.0.0 and 3.0.1. I might even discover a bug fix for wxWidgets.
PRL