Get quick announcements through the RSS feed http://www.codeblocks.org/nightly/CodeBlock_RSS.xml
Before you use a nightly make sure you understand how it works (http://forums.next.codeblocks.org/index.php/topic,3232.0.html).
A link to the unicode windows wxWidget dll(s) for Code::Blocks : https://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/wxmsw31u_gcc_cb_wx313_2D_gcc810-mingw64.7z
A link to Mingw64 dll's needed by Code::Blocks : http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/Mingw64dlls8.1.0.7z
The 18 January 2020 build is out.
- Windows :
http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/2020/CB_20200118_rev11954_win64.7z
- Linux :
none
The current SDK version is : 1.46.0
Resolved Fixed:
- editor: Style for indent guides is not applied correctly if some of the colours is using the default color
- add support for upcoming standard C++20 and upcoming gcc 10
- updated docs according http://forums.next.codeblocks.org/index.php/topic,23614.0.html (thanks gd_on)
- lexer: Add f-strings to the python lexer (thanks Quiss)
- applied patch #805: Flashing icons in Windows' taskbar while starting C::B. Thanks Miguel Gimenez.
- sdk: Hide the implementation of the encoding detector
- applied patch #910: Correction of assert and build error in loghacker plugin. Thanks Miguel Gimenez.
Regressions/Confirmed/Annoying/Common bugs:
a patched wx 3.1.3 has been made, so you will need to download the new cb wx 3.1.3 dll's
Name : Code::Blocks
Version : svn-r11936
It's svn rev.11936
och shit you are right, oh damn, I forgot to svn up, och boy, how stupid :-(
new build should be in place now.
Name : Code::Blocks
Version : svn-r11951
Ok, thanks!
Thanks, applying now.
Hi
OS X version of this rev can be downloaded from my Google Drive (https://drive.google.com/open?id=0B2rFQ8rNHzEeN0xtU3R6emdhUWs) (needs at least OS X 10.15)
Debian Stretch and Buster (32 and 64 bits) can be installed from my repo (https://wxstuff.xaviou.fr/article/debian-repository.html).
Regards
Xav'
Quoteapplied patch #805: Flashing icons in Windows' taskbar while starting C::B. Thanks Miguel Gimenez.
Oh, finally! Special thanks for this patch.
This version shows svn 11951
I always take the number of svn at the time I create the build, normally this matches, this time it does not, because the last 3 commits occurred on another branch.
Thank you for this build! It looks like the problem I reported with IncrementalSearch in the previous nightly (http://forums.next.codeblocks.org/index.php/topic,23606.msg161046.html#msg161046) is now gone (Win10).
The Incremental Search problem is gone in the nightly, but not in the SVN head version. May be related to this?
Quote from: killerbot on January 18, 2020, 09:02:17 PM
a patched wx 3.1.3 has been made, so you will need to download the new cb wx 3.1.3 dll's
@Miguel Gimenez This is the price we should pay for using the dev version of wx. :(
Who is using it?. I'm using the official wx3.1.3 release.
Now and then I use the wx development version, trying to find regressions, but bug reports and patches for C::B are made using the official release.
If the nightly's library is different from the release it would be cool to know what has changed.
It is up to killerbot to post the details. He is building it. ;)
will post them this evening.
@Killerbot :
in the announcement of a nightly you have a special paragraph "Regressions/Confirmed/Annoying/Common bugs:" which is generally empty.
It could be nice to tell here that for some (may be still unknown) reasons some plugins have been temporarily disabled because they produce errors.
gd_on
PS : the bug described on IncrementalSearch behaviour seems to have disappeared in wxWidgets 3.1.4 (git version)
Quote from: gd_on on January 23, 2020, 09:41:29 AM
PS : the bug described on IncrementalSearch behaviour seems to have disappeared in wxWidgets 3.1.4 (git version)
The commit that broke the plugin was reverted soon after, but wx3.1.3 was released before reversion took place; see
http://forums.next.codeblocks.org/index.php/topic,23606.msg161103.html#msg161103 (http://forums.next.codeblocks.org/index.php/topic,23606.msg161103.html#msg161103)
What is the suggested approach for testing the nightly build? (Debian x64)
Since I am still using the official released version, and this will be the last version in the repository for ever.
As I use the program regularly I want to build it, evaluate if moving is the right way, and then move to this version.
This way updating is "controlled".
Can C::B be compiled in a single folder and run? before running the install?
Yes, pass --prefix to the configure script. I use --prefix=/home/myuser/software/cb.
Another option is to build packages using the standard debian command for this. We have all the files needed, so building packages is a single command and it should be reliable.
A tiny gripe...
Unmentioned in the changes for this nightly is the inclusion of a new? plugin called 'Header guard'. Unfortunately it appears to be enabled by default and makes unexpected and unwanted changes to my header files. I eventually tracked down the cause but it would be useful in future to highlight such additions and not enable them by default. I've got 3 machines that I use, each of which have 3+ CodeBlocks profiles, so thats 9+ instances that I need to make manual changes to to prevent this behavior.
Otherwise, thank you for another great nightly with a number of useful improvements!
Andy
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.
I have seen a strange bug in the editor a couple of times in this release:
1. In a C++ header file within a class declaration, go to a blank line and type
private:
2. Press <Return> key, you then end up with
private:private
See attachment. Why does this happen?
Quote from: trivia21 on January 29, 2020, 11:04:02 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.
That happens when wxWidgets reports a non-existent menu id. That menu is dynamic and probably has unique (new) menu items assigned as it is built, ie., unknown to KeyBinder.
I'll look into it.
cacb:
Can you try to reproduce it with a simple project?
What happens if you do this in a function?
Does case statements work correctly?
What are your editor settings?
Can you try the previous night build to be sure it is not an old problem?
Quote from: trivia21 on January 29, 2020, 11:04:02 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.
Quote from: killerbot on January 23, 2020, 07:16:18 AM
will post them this evening.
Hi, killerbot, did you post it somewhere?
I don't see this information in this thread.
forgot about it, will do when I reboot into my windows (probably tomorrow), my apologies for the delay.
these are the adjustments I carry out on the wx :
1) include/wx/msw/setup.h (for the 2D support)
#if defined(_MSC_VER) && _MSC_VER >= 1600
#define wxUSE_GRAPHICS_DIRECT2D wxUSE_GRAPHICS_CONTEXT
#else
#define wxUSE_GRAPHICS_DIRECT2D 0
#endif
==> just 1 line
#define wxUSE_GRAPHICS_DIRECT2D wxUSE_GRAPHICS_CONTEXT
2) combo.h and combocmn.cpp
Quote
This is the offending commit: Make wxComboCtrl a wxCompositeWindow
https://github.com/wxWidgets/wxWidgets/commit/70e9dbd756cb321fb85d6380b3e37bcd59604e09
This commit was reverted after wx3.1.3 release in commit https://github.com/wxWidgets/wxWidgets/commit/6b00cc80f1fdb3ef134e2df694a0c34905442042
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).
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)
Quote from: zinsser 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)
See this post: Alert message box jumps if I open the compiler setting dialog (http://forums.next.codeblocks.org/index.php/topic,23567.msg160561.html#msg160561)
and this post: Re: The 15 December 2019 build (11927) is out. (http://forums.next.codeblocks.org/index.php/topic,23606.msg161166.html#msg161166)
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.
Quote from: ollydbg on February 11, 2020, 07:35:25 AM
See this post: Alert message box jumps if I open the compiler setting dialog (http://forums.next.codeblocks.org/index.php/topic,23567.msg160561.html#msg160561)
and this post: Re: The 15 December 2019 build (11927) is out. (http://forums.next.codeblocks.org/index.php/topic,23606.msg161166.html#msg161166)
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.
@killerbot: I guess we want to have this patch in our version, too. What do you think?
ok will take it in with a next nightly
Quote from: Pecan on February 03, 2020, 07:58:16 PM
Quote from: trivia21 on January 29, 2020, 11:04:02 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.
Quote from: ollydbg on February 11, 2020, 07:35:25 AM
Quote from: zinsser 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)
See this post: Alert message box jumps if I open the compiler setting dialog (http://forums.next.codeblocks.org/index.php/topic,23567.msg160561.html#msg160561)
and this post: Re: The 15 December 2019 build (11927) is out. (http://forums.next.codeblocks.org/index.php/topic,23606.msg161166.html#msg161166)
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.
@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.
Quote from: oBFusCATed 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.
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.