Author Topic: The 18 January 2020 build (11954) is out.  (Read 14223 times)

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5239
Re: The 18 January 2020 build (11954) is out.
« Reply #30 on: February 08, 2020, 10:56:52 am »
from wx roadmap :

 New development happens on 3.1 branch. The latest version is 3.1.3, released on October 28, 2019 and we plan to release one last 3.1.4 release in 3.1.x series in the beginning of 2020 with 3.2.0 follwowing soon afterwards.

One of the big planned changes for this 3.2 is better support for high DPI displays, but there are, of course, many, many other fixes and improvements in it as well.

3.2 will also finally drop support for very old legacy systems (such as Win9x platform) and compilers (MSVC6, maybe MSVC7 as well).

Offline zinsser

  • Single posting newcomer
  • *
  • Posts: 2
Re: The 18 January 2020 build (11954) is out.
« Reply #31 on: February 11, 2020, 04:49:34 am »
I have found a bug when setting font of editer:

Steps to reproduce:
1. open CB.
2. settings -> editor -> general settings -> font -> choose -> OK. (do nothing) > OK
3. settings -> editor

an assert is raised (see attachment)

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 5234
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Re: The 18 January 2020 build (11954) is out.
« Reply #32 on: February 11, 2020, 07:35:25 am »
I have found a bug when setting font of editer:

Steps to reproduce:
1. open CB.
2. settings -> editor -> general settings -> font -> choose -> OK. (do nothing) > OK
3. settings -> editor

an assert is raised (see attachment)

See this post: Alert message box jumps if I open the compiler setting dialog
and this post: Re: The 15 December 2019 build (11927) is out.

Specially, this bug is fixed in the wx's official git head, but not in wx 3.1.3 release.
I think we have to manually apply this patch to the official wx3.1.3 release.
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

Offline zinsser

  • Single posting newcomer
  • *
  • Posts: 2
Re: The 18 January 2020 build (11954) is out.
« Reply #33 on: February 11, 2020, 09:07:36 am »

See this post: Alert message box jumps if I open the compiler setting dialog
and this post: Re: The 15 December 2019 build (11927) is out.

Specially, this bug is fixed in the wx's official git head, but not in wx 3.1.3 release.
I think we have to manually apply this patch to the official wx3.1.3 release.


thank you for the information!
I will update wx3.1.3 to solve this problem.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 12682
    • Travis build status
Re: The 18 January 2020 build (11954) is out.
« Reply #34 on: February 11, 2020, 07:36:20 pm »
@killerbot: I guess we want to have this patch in our version, too. What do you think?
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5239
Re: The 18 January 2020 build (11954) is out.
« Reply #35 on: February 11, 2020, 07:55:10 pm »
ok will take it in with a next nightly

Offline trivia21

  • Single posting newcomer
  • *
  • Posts: 9
Re: The 18 January 2020 build (11954) is out.
« Reply #36 on: February 18, 2020, 09:56:23 am »
In Settings/Editor/Keyboard shortcuts when I try to add a shortcut for View/Perspectives/Code::Blocks default or minimal, I get the error message "KeyBinding file corrupted. Please delete" and the setting is not applied.

Ubuntu 18.04, this nightly build with official wx3.1.1.

Fixed; svn r11957
The menu item label contained "::" within "Code::Blocks" text caused the scan routine to fail.
Thank you, it works now.

Offline Pecan

  • Plugin developer
  • Lives here!
  • ****
  • Posts: 2250
Re: The 18 January 2020 build (11954) is out.
« Reply #37 on: June 16, 2020, 08:33:40 pm »
I have found a bug when setting font of editer:

Steps to reproduce:
1. open CB.
2. settings -> editor -> general settings -> font -> choose -> OK. (do nothing) > OK
3. settings -> editor

an assert is raised (see attachment)

See this post: Alert message box jumps if I open the compiler setting dialog
and this post: Re: The 15 December 2019 build (11927) is out.

Specially, this bug is fixed in the wx's official git head, but not in wx 3.1.3 release.
I think we have to manually apply this patch to the official wx3.1.3 release.

Where is the fix for this bug so we can add it to our own widgets 3.1.3.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 12682
    • Travis build status
Re: The 18 January 2020 build (11954) is out.
« Reply #38 on: June 17, 2020, 01:52:09 am »
@Pecan: Killerbot already patched our version. From here https://trac.wxwidgets.org/ticket/18590 you can find the commit. If you're talking about the font issue.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline Pecan

  • Plugin developer
  • Lives here!
  • ****
  • Posts: 2250
Re: The 18 January 2020 build (11954) is out.
« Reply #39 on: June 17, 2020, 07:03:38 pm »
@Pecan: Killerbot already patched our version. From here https://trac.wxwidgets.org/ticket/18590 you can find the commit. If you're talking about the font issue.

I was getting the font assert with virgin wx313 (described in these messages).
I applied this patch to my local wxWidgets313.
https://github.com/wxWidgets/wxWidgets/commit/a73194f6b448b047168c566e48837957d08d2165

It solved the problem.