This and your other SVGFileDC issues are wxWidgets problems, not wxPython-specific. Please create tickets for them, if they are not already there at https://trac.wxwidgets.org/
···
–
Robin
On Tuesday, March 19, 2019 at 5:00:58 PM UTC-7, ABC wrote:
It looks like those changes were not backported to the WX_3_0_BRANCH, so they are not included in wxPython 4.0.x. wxPython 4.1 (in progress now) will be using wxWidgets’ 3.1.x series and so those changes will be included then.
···
On Wednesday, March 20, 2019 at 8:34:46 AM UTC-7, ABC wrote:
Thanks Robin. I checked. In 2016, SVGFileDC was thoroughly fixed in wx.Widgets (drawing lines, arcs, text, the whole thing…).
The version of wxPython that I’m using reports itself with wx.version() to be
Alternatively, you could also request that they be backported to wxWidgets 3.0.x, assuming Robin ever plans another 4.0.x release.
Scott
···
On Wed, 20 Mar 2019, Robin Dunn wrote:
On Wednesday, March 20, 2019 at 8:34:46 AM UTC-7, ABC wrote:
Thanks Robin. I checked. In 2016, SVGFileDC was thoroughly fixed
in wx.Widgets (drawing lines, arcs, text, the whole thing...).
The version of wxPython that I'm using reports itself with
wx.version() to be
"4.0.3 msw (phoenix) wxWidgets 3.0.5".
It looks like those changes were not backported to the WX_3_0_BRANCH, so
they are not included in wxPython 4.0.x. wxPython 4.1 (in progress now) will
be using wxWidgets' 3.1.x series and so those changes will be included then.
Thanks for confirming these issues!
Robin, do you plan on another 4.0.x, or will 4.1 be the next one - and
roughly when?
···
On Wed, Mar 20, 2019 at 10:25 AM Scott Talbert <swt@techie.net> wrote:
On Wed, 20 Mar 2019, Robin Dunn wrote:
> On Wednesday, March 20, 2019 at 8:34:46 AM UTC-7, ABC wrote:
> Thanks Robin. I checked. In 2016, SVGFileDC was thoroughly fixed
> in wx.Widgets (drawing lines, arcs, text, the whole thing...).
> The version of wxPython that I'm using reports itself with
> wx.version() to be
> "4.0.3 msw (phoenix) wxWidgets 3.0.5".
>
>
> It looks like those changes were not backported to the WX_3_0_BRANCH, so
> they are not included in wxPython 4.0.x. wxPython 4.1 (in progress now) will
> be using wxWidgets' 3.1.x series and so those changes will be included then.
Alternatively, you could also request that they be backported to wxWidgets
3.0.x, assuming Robin ever plans another 4.0.x release.
There have been a few fixes in the 4.0 branch, so there probably will be a 4.0.5. I’ve been busy with several other things lately and haven’t had a lot of time for working on the project, so the timeline for either release is unknown at the moment.
···
On Wednesday, March 20, 2019 at 10:55:16 AM UTC-7, ABC wrote:
Thanks for confirming these issues!
Robin, do you plan on another 4.0.x, or will 4.1 be the next one - and
Robin, I understand the constraints on your time, and I appreciate your
support for wxPython.
Is there any way to bring wxWidget's fixes to SVG into the 4.0.5 release?
There are two main branches of wxWidgets:
3.0.x (git branch = WX_3_0_BRANCH) - this is the "stable" release branch.
3.1.x (git branch = master) - this is the "development" release branch.
The latest release of the 3.0.x branch is 3.0.4, but wxPython pulls in directly from the WX_3_0_BRANCH and not from 3.0.x releases. That's why wxPython reports 3.0.5, since it is pulling from the head of the WX_3_0_BRANCH.
You need to request the updates be backported from master to WX_3_0_BRANCH. Note that it may not be possible to backport those changes if they involved ABI changes.
Scott
···
On Fri, 22 Mar 2019, ABC wrote:
I updated my wxPython to 4.0.4, and get this version message:
4.0.4 msw (phoenix) wxWidgets 3.0.5
