News:

Accounts with zero posts and zero activity during the last months will be deleted periodically to fight SPAM!

Main Menu

The 31 January 2015 build (10091) is out.

Started by killerbot, January 31, 2015, 11:02:02 AM

Previous topic - Next topic

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 for Code::Blocks : http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/wxmsw28u_gcc_cb_wx2812_gcc481-TDM.7z

For those who might need this one (when no MingW installed on your system) : the mingw10m.dll : http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/mingwm10_gcc481-TDM.7z

The 31 January 2015 build is out.
  - Windows :
   http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/2015/CB_20150131_rev10091_win32.7z
  - Linux :
   none

The current SDK version is : 1.24.0

Resolved Fixed:


  • CCManager: allow overloaded calltip navigation by arrow keys (patch by darmar; modified)
  • CCManager: enable colour configuration of tooltips (patch by scarphin)
  • fixed compilation error with wx30+ due to use of deprecated wxWidgets API
  • compiler options: Fix the clear button in the Search directories tab (partially revert r7569)
  • NassiPlugins: Fix issue #124 Match diagram colors to editor colors Edit (patch by scarphin, modified)
  • FileManager: 1. adds support for providing git status decorators (clunky because we need a more complete set of status codes for modern VCSs) 2. Corrects labels for status decorator settings in default.conf for HG and BZR (they were reversed).
  • ccmanager: Make the call tips wrap around

Regressions/Confirmed/Annoying/Common bugs:




Jenna

#1
Svn r10090 is out since some days, r10091 is currrently compiling (status of rpm-build: https://copr.fedoraproject.org/coprs/jenslody/codeblocks/monitor/ ).
The only difference between both revisions is the wrap-stuff in calltips.

All build and online.

Debian packages (binaries and sources) for 32-bit and 64-bit systems can be found in my debian-repo.
Fedora packages (binaries and sources) for 32-bit and 64-bit systems (fc19, fc20, fc21 and rawhide), RedHat/CentOS 5 and 6 packages (also 32-bit and 64-bit) and RedHat/CentOS 7 packages (only 64-bit at the moment) can be found in my rpm-repo.
I recently switched to copr to build and host my Fedora and CentOS packages.
Instructions how to use it can be found on my server (easier) or on copr (a little more handwork needed).

By the way:
users who did not add my rpm-repo manually but by downloading the appropriate rpm (with my repo-file inside) should get an automatic update to the new repo.

ollydbg

Bug: I see a tooltip always show in the windows, it covers every applications on my windows XP.
See image below

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.

Alpha

Quote from: ollydbg on February 01, 2015, 04:57:57 AM
Bug: I see a tooltip always show in the windows, it covers every applications on my windows XP.
Oh no... I thought I dealt with every case of this during the CC framework refactor.  (Assuming this only recently started), are you able to figure out which revision introduced this?

shurick

Packages for openSUSE (binaries and sources) for 32-bit and 64-bit.
Packages for openSUSE http://codeblocks.esy.es  (binaries and sources) for 32-bit and 64-bit.

zak


Hi,

under Win 7 C:B crashes during debug when I try any kind
of interaction with the whatches windows.

Reinstallation from scratch does not resolved the problem.

Please fix it if possible.

GZ


   

BlueHazzard

Quote from: zak on February 02, 2015, 02:33:26 PM

Hi,

under Win 7 C:B crashes during debug when I try any kind
of interaction with the whatches windows.

Reinstallation from scratch does not resolved the problem.

Please fix it if possible.

GZ

please provide more info, because for me it is working without crash...
* the most important would be the output of the debugger window
* a minimal example, to reproduce the bug
* exact steps to reproduce the bug

Alpha

Quote from: Alpha on February 01, 2015, 05:57:05 AM
Quote from: ollydbg on February 01, 2015, 04:57:57 AM
Bug: I see a tooltip always show in the windows, it covers every applications on my windows XP.
Oh no... I thought I dealt with every case of this during the CC framework refactor.  (Assuming this only recently started), are you able to figure out which revision introduced this?
Erm, possibly more importantly, how did you manage to trigger this?  I cannot seem to.

ollydbg

Quote from: Alpha on February 04, 2015, 01:04:55 AM
Quote from: Alpha on February 01, 2015, 05:57:05 AM
Quote from: ollydbg on February 01, 2015, 04:57:57 AM
Bug: I see a tooltip always show in the windows, it covers every applications on my windows XP.
Oh no... I thought I dealt with every case of this during the CC framework refactor.  (Assuming this only recently started), are you able to figure out which revision introduced this?
Erm, possibly more importantly, how did you manage to trigger this?  I cannot seem to.
Hi, Alpha, I will report the steps to trigger this bug, but it is really hard to reproduce this. (I just tried for a while, and can't reproduce it)
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.

nenin

I have strong suspects that this bug is originated from kind of interference between wxWindows and NVidia driver (and may be VCL). I observe similar effects with other wx-based software.  It can not be bold reproduced, it just appears from time to time.

OsminohejTygr

Quote from: nenin on February 05, 2015, 10:43:10 AM
I have strong suspects that this bug is originated from kind of interference between wxWindows and NVidia driver (and may be VCL). I observe similar effects with other wx-based software.  It can not be bold reproduced, it just appears from time to time.

This bug manifests itself on Intel drivers as well. Also it's there for quite a long time. But it's not so annoying because it's very rare (at least for me).

BlueHazzard

i mainly can observe this as soon as c::b "hangs" (ex. it loads the debugger), you trigger the popup and switch to a other window.

ollydbg

Quote from: BlueHazzard on February 06, 2015, 07:11:46 PM
i mainly can observe this as soon as c::b "hangs" (ex. it loads the debugger), you trigger the popup and switch to a other window.
Oh, yes, it happens when I am debugging or start debugging.
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.

ollydbg

Another bug I see in the doxygen plugin's toolbar becomes much smaller, see the screen shot below:
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.

zak


now, watches window works very well! version: 10122

Thanks!!!