The 09 March 2019 build (11579) is out.

[killerbot]

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.

A link to the unicode windows wxWidget dll(s) for Code::Blocks : http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/wxmsw31u_gcc_cb_wx311_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 09 March 2019 build is out.
  - Windows :
   http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/2019/CB_20190309_rev11579_win64.7z
  - Linux :
   none

The current SDK version is : 1.37.0

Resolved Fixed:

• InfoWindow: Log the info message to the main log
• CppCheck: Fix crash when the generated xml is missing (thanks blauzahn)
• sdk: Fix memory leak when showing the "choose compiler" dialog, because the current compiler is not available
• CC: fix #25 Casting a function call to void breaks parser
• CC: fix SF #176 Code completion fails with enums whose underlying types
• wxSmith: fix wxImagePanel preview error if empty image is used.
• wxSmith: fix "dangling" frames which cause C::B process alive after C::B closed
• CC: fix parsing of function declaration which returns enum type
• ThreadSearch: Fix overwriting of search mask on windows (thanks Miguel Gimenez)
• ThreadSearch: Use file filter mask for all search options, not only for search in directories
• ThreadSearch: Use file filter mask for all search options, not only for search in directories
• UI: Make it possible to assign a keyboard shortcut to Build -> Select target -> Select target...

Regressions/Confirmed/Annoying/Common bugs:

[Xaviou]

Hi

OS X version of this rev can be downloaded from my Google Drive.

Debian Stretch (32 and 64 bits) can be installed from my repo.

Regards
Xav'

[raynebc]

It's very nice to see the void casting bug fixed in this release.  I don't immediately see that Hunspell is actually included with Firefox 65.x on Windows, it seems to ship with a different kind of dictionary as there is no dictionary folder in the browser's install folder, and nothing obviously relevant in my Firefox profile folder.  Manually installing the Hunspell dictionary plugin for Firefox (https://addons.mozilla.org/en-US/firefox/addon/us-english-dictionary/) didn't provide something that is obviously (to me) usable in C::B.  Is there some no-effort way to get the spell checker going like it was out-of-the-box in older nightly builds?

Also, I find that when I use ALT+F, S to invoke the save function (a habit I have so I don't have to move my left hand from the home row), it saves, but it also brings up a dialog asking me to enter a name for the template.  It seems like it incorrectly invokes the "Save project as template" function in this scenario?

[stahta01]

Spellcheck not work:

Khram refuses to supply requested information.

Tim S.

[BlueHazzard]

Spellcheck not work:

Khram refuses to supply requested information.

Tim S.

I am working on it. He provided example files here http://forums.next.codeblocks.org/index.php/topic,23102.msg157663.html#msg157663
I can reproduce the error on windows now, but it is hard for me to fix it...

It's very nice to see the void casting bug fixed in this release.  I don't immediately see that Hunspell is actually included with Firefox 65.x on Windows, it seems to ship with a different kind of dictionary as there is no dictionary folder in the browser's install folder, and nothing obviously relevant in my Firefox profile folder.  Manually installing the Hunspell dictionary plugin for Firefox (https://addons.mozilla.org/en-US/firefox/addon/us-english-dictionary/) didn't provide something that is obviously (to me) usable in C::B.  Is there some no-effort way to get the spell checker going like it was out-of-the-box in older nightly builds?

My codeblocks finds the dictionaries from libre office and works out of the box

[raynebc]

Is installing Open/Libre Office the lowest effort way to get a compatible Hunspell install then?

[stahta01]

Is installing Open/Libre Office the lowest effort way to get a compatible Hunspell install then?

Do these directions no longer work?
http://wiki.codeblocks.org/index.php?title=SpellChecker_plugin&plugin=

Edit: I am guessing having "OpenOffice 4.1.5" installed is why it works for me.

Tim S.

[raynebc]

Firefox (at least the version I'm using, 65.0.1) has no dictionaries folder in it's installation path.  The Hunspell page's hints about installing the dictionary via a Firefox add-on doesn't make a dictionary available for CodeBlocks's use in a way that's obvious to me.  It seems like I would need to either install some unrelated third party software or build Hunspell from source, which is certainly more involved than installing OpenOffice.  Older builds came with the spell checker built-in, is that something that's not coming back?  Will the spell checker be included by default in future full releases?

[BlueHazzard]

or build Hunspell from source

Why would you want to build hunspell from source? The only thing you need are dictionaries. Codeblocks provides the binaries, but not the dictionaries... You can download from here https://github.com/wooorm/dictionaries , or you download the dictionary extensions from libre office or open office, extract them like a zip archive and only use the dictionaries from inside them, no need to install some office suite...

Will the spell checker be included by default in future full releases?

The spell checker should be included by default (if nothing went wrong with this nightly, i did no checked it) but you have to provide the dictionary for your language, as it always was...

[raynebc]

I didn't have to manually install one previously, Code::Blocks automatically selected or came with it.  When I launch C::B 17.12, the Editor options confirm that it is using the dictionary that it came with at share\codeblocks\SpellChecker.  Included in this folder is a file called "en_US.dic".  I guess I'll have this nightly use that dictionary, if you believe that will work.

A bigger problem though is that this nightly build fails assertion and then crashes on launch if it is started during a Remote Desktop session.  A C::B session I had already opened crashed immediately after I remote desktopped into the computer.  This is a show stopper for me and I'll have to downgrade to 17.12.  I hadn't used any of the nightlies since that release, so I don't know which other nightlies may be similarly affected.  The assert message is as follows:

===
A debugging check in this application has failed.

../../src/msw/bitmap.cpp(1346): assert "" Assert failure"" failed in GetRawData(): incorrect bitmap type in wxBitmap::GetRawData()
===

If I click continue instead of stop, this alert dialog message is diplayed:
===
A debugging check in this application has failed.

../../src/msw/bitmap.cpp(272): assert "!m_dib" failed in Free(): forgot to call wxBitmap::UngetRawData()!
===

Continuing to click Continue just repeatedly alternates between these two messages, possibly indefinitely, until stop is clicked and the program is allowed to crash.

[sphinx66]

insert/refractor don't work   :'(

[oBFusCATed]

Continuing to click Continue just repeatedly alternates between these two messages, possibly indefinitely, until stop is clicked and the program is allowed to crash.

On linux there is a checkbox to ignore further asserts of this type. Isn't this the case on windows?
Does the assert window provide a backtrace?

There are hundreds of images in code::blocks and without more info it will be hard to find out what is going on.

[Xaviou]

insert/refractor don't work   :'(

Works fine for me on Windows 10 Pro 64bits.

[raynebc]

There's a "don't show this dialog again" checkbox in the Windows release, I just didn't want to use that if it would suppress the message even in future launches of the program (in case I could help troubleshoot).  I found that if I did click Continue 34 times it did get into the IDE eventually.  I went into the editor settings and pointed the spell checker dictionary to the one that came with Codeblocks 17.12.  After re-launching the IDE, going back into the editor settings, selecting US English for the dictionary and clicking OK, a wxWidgets debug alert window was displayed saying:

===
A debugging check in this application has failed.

../../src/common/wincmn.cpp(1531): asesert ""Assert failure"" failed in RemoveEventHandler(): where has the event handler gone?
===

Clicking continue allows the editor dialog to close.  Going back into the spell checker settings shows that the dictionary path and language were retained.  However I can't tell that the spell checker is working.  Intentionally misspelled comments are not being underlined like older versions of CodeBlocks I've used, and there is no context menu item for the spell checker.  SpellChecker 0.1 is listed as enabled in the manage plugins dialog, and the cited DLL file exists as the listed path of share\CodeBlocks\plugins\SpellChecker.dll.

I don't see a backtrace offered with any of the assert dialog messages I've mentioned.

[oBFusCATed]

There's a "don't show this dialog again" checkbox in the Windows release, I just didn't want to use that if it would suppress the message even in future launches of the program (in case I could help troubleshoot).

This is not something that is preserved between launches.

I found that if I did click Continue 34 times it did get into the IDE eventually.

Can you try to disable some plugins to try to find if it is a plugin causing these asserts?