Code::Blocks Forums

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 : 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 07 April 2019 build is out.
  - Windows :
   http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/2019/CB_20190407_rev11623_win64.7z
  - Linux :
   none

The current SDK version is : 1.37.0

Resolved Fixed:

• UI: Move toolbar images from src/resource/images to src/resource/images/22x22
• UI: Move toolbar images from plugins/compilergcc/src/resources/images/ to src/resourceplugins/compilergcc/src/resources/images/22x22/
• UI: Make the xrc wxToolbarAddon handler to be able to remap bitmap paths
• UI: Make MainFrame::DoFixToolbarsLayout to really work when toolbar size changes
• UI: Fit toolbars on every load
• UI: Print warning message when a toolbar image requires resizing
• UI: Move images for the BrowseTracker's toolbar in 22x22 subfolder as done for the core
• UI: Move images for the IncrementalSearch's toolbar in 22x22 subfolder as done for the core
• UI: Prepare the ThreadSearch plugin to support more than to resolutions of UI images
• UI: Move images for the DoxyBlocks's toolbar in 22x22 subfolder as done for the core
• UI: Remove more places in ThreadSearch which used the /environment/toolbar_size instead of GetImagePrefix
• UI: Add 32x32 images for main and debugger toolbars (thanks Specialmart for the new icons)
• UI: Add the possibility to select toolbars which are 32x32 big
• UI: Make toolbars work on retina mac machines
• UI: Add 32x32 images for the rest of plugins which create toolbars (thanks Specialmart for the images)
• UI: Reenable the dpi aware flag on windows
• UI: Do not call Realize toolbars for every disabled tool in a xrc file
• UI: Print config file path as the first line in the list ctrl for the main log
• UI: Make toolbars on wx3.1 and GTK3 to almost look sharp
• UI: Make the images in ThreadSearch's toolbar to work correctly on GTK+ 3 and scaling of 2x
• UI: Add wrapper for wxWindow::GetContentScaleFactor to make it easier to use this call
• UI: Fix build for wx2.8
• UI: Fix wx3.0.x gtk3 builds
• UI: Make toolbar images for DoxyBlocks work correctly when using GTK+3 on HiDPI (scale >= 2) monitor
• UI: Do not use scalingFactor on Windows
• DragScroll - Add user config option to reverse mouse wheel zoom

Regressions/Confirmed/Annoying/Common bugs:

Hi

OS X version of this rev can be downloaded from my Google Drive (https://drive.google.com/open?id=0B2rFQ8rNHzEeN0xtU3R6emdhUWs).

Debian Stretch (32 and 64 bits) can be installed from my repo (https://wxstuff.xaviou.fr/article/debian-repository.html).

Toolbars icons seems to not have supported the last commits  ;)
See attached screenshots made on OSX

Regards
Xav'

Works fine on macOS, you just have to use 32x32 icons. I've not changed the default yet or I've not added some logic to auto select the correct resolution according to the scaling factor.

Quote from: oBFusCATed on April 07, 2019, 05:12:20 PM
Works fine on macOS, you just have to use 32x32 icons.

Works fine : thank you for the tip.

Regards

Xav'

Thank you for this new version.

Problem with : Vista Business Pack 2 32bits :  TDM-GCC 4.9.2, C::B  : svn11623, wxwidgets2.8, 
with 'void MainFrame::CreateIDE()' at line  758:75

QuoteU:\Donnees\Svn_Compile\Cb\Tdm492\cb-11623\src\src\main.cpp:758:75:
error: cannot pass objects of non-trivially-copyable type 'class wxString' through '...'

While waiting for your solution, I propose you:
char *  txt =  wxMBSTRINGCAST (CfgMgrBldr::Get()->GetConfigFile().ToAscii());
wxString msg = wxString::Format(wxT("Loaded config file '%s'"), txt);
                               // CfgMgrBldr::Get()->GetConfigFile());

which works in my case.

Regards.

Quote from: oBFusCATed on April 07, 2019, 05:12:20 PM
Works fine on macOS, you just have to use 32x32 icons.

It is not possible to select 32x32 tool icons on Windows 7 x64 SP1. And selecting 16x16 isn't possible either. The radio-check just cleared after you reopen the wxSmith settings dialog.
And icons on buttons are gone... :(
And when saving project WXS-file was removed from the list of units... :(

QuoteIt is not possible to select 32x32 tool icons on Windows 7 x64 SP1

Works for me in the same environment but compiled with wx3.1.2 in 32 bits.

Hi,

got multiple debug alert; first one bitmap.c(841), dib.cpp(134) and image.cpp(2112). See attachments.

RPT attached also.

Win 7 SP1, 64-bit.

Quote from: Miguel Gimenez on April 08, 2019, 11:51:28 AM

QuoteIt is not possible to select 32x32 tool icons on Windows 7 x64 SP1

Works for me in the same environment but compiled with wx3.1.2 in 32 bits.

Setting 32x32 works for me on Windows 7 x64 SP1 [Version 6.1.7601].
Used this nightly build to test.

Tim S.

@damorin, which icon size are you using?
Your report indicates the problem happens when attaching the Fortran Project plugin, probably an image is corrupted or missing.
In fact the images/32x32 folder has three PNG while the others have four, and images/fortranproject/32x32 has 28 images while the others have 44.

I have problems enabling the Thread Search Plugin with this Nightly on Windows 7.
No idea if it is a new problem or not I just tried to enable all the plugins and its the only one that failed for me.

Edit: Problem also exists in rev11552

Tim S.

Quote from: Miguel Gimenez on April 08, 2019, 04:03:29 PM
@damorin, which icon size are you using?
Your report indicates the problem happens when attaching the Fortran Project plugin, probably an image is corrupted or missing.
In fact the images/32x32 folder has three PNG while the others have four, and images/fortranproject/32x32 has 28 images while the others have 44.

Hi Miguel,

I never set the icon size; it's still the same setting as first installation (years ago).

I reverted to version svn 11579 since it's no more usable.

Currently the tools icons size is set to '16x16 - Small' and Setting is set to '80x80 - Large'.

Also, I've never used the Fortran plugin.

R.

QuoteI've never used the Fortran plugin

But you have it enabled, right?. Can you disable it using 11579 and then try the nightly?

I have no crash with the current nightly, however, DoxyBlocks and ThreadSearch toolbars contains no images. Some images used by FortranProject plugin are not shown too. The problem is that folder "<C::B folder>/share/CodeBlocks/images" does not contain DoxyBlocks, ThreadSearch, fortranproject, wxsmith folders. Manuall copying these folders does help.

Hm, I guess I've not tested the build in output31_64 :(
Can someone verify that the devel31_64 and output31_64 differ in content?

travelling, at ACCU, will check my build setup when I am back home, after the weekend.

Quote from: darmar on April 10, 2019, 09:53:33 PM
I have no crash with the current nightly, however, DoxyBlocks and ThreadSearch toolbars contains no images. Some images used by FortranProject plugin are not shown too. The problem is that folder "<C::B folder>/share/CodeBlocks/images" does not contain DoxyBlocks, ThreadSearch, fortranproject, wxsmith folders. Manuall copying these folders does help.

my devel31_64\share\CodeBlocks\images does contain them, and each have 3 subdirs containing files.

and indeed  :output31_64\share\CodeBlocks\images is missing many subdirs (codesnippets, DoxyBlocks, fortranproject, Threadsearch, wxsmith)
I ran update31_64.bat once more ==> result stays the same ...

These folders are never updated by the src/update*.bat scripts. They are updated by the src/plugins/contrib/ThreadSearch/update*.bat scripts.

What is the output in the build log if you build the ThreadSearch plugin from the workspace?

This problem happens if you build first, then delete the output31_64 folder and then run the update script.

I've updated both update31_64.bat and update/update30 files now they are similar in look and function. If anyone is interested in using the other versions patches are welcomed...

Please let me know if you have problems with this new version of the script. Now it should work even if the output31_64 folder is deleted after a build.