The 18 January 2020 build (11954) is out.

[oBFusCATed]

It is up to killerbot to post the details. He is building it.

[killerbot]

will post them this evening.

[gd_on]

@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)

[Miguel Gimenez]

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

[Jewest]

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?

[oBFusCATed]

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.

[AndyJ]

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

[trivia21]

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.

[cacb]

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?

[Pecan]

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.

[oBFusCATed]

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?

[Pecan]

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.

[ollydbg]

will post them this evening.

Hi, killerbot, did you post it somewhere?
I don't see this information in this thread.

[killerbot]

forgot about it, will do when I reboot into my windows (probably tomorrow), my apologies for the delay.

[killerbot]

these are the adjustments I carry out on the wx :

1) include/wx/msw/setup.h   (for the 2D support)

Code Select Expand


#if defined(_MSC_VER) && _MSC_VER >= 1600
    #define wxUSE_GRAPHICS_DIRECT2D wxUSE_GRAPHICS_CONTEXT
#else
    #define wxUSE_GRAPHICS_DIRECT2D 0
#endif


==> just 1 line

Code Select Expand


    #define wxUSE_GRAPHICS_DIRECT2D wxUSE_GRAPHICS_CONTEXT


2) combo.h and combocmn.cpp

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