Code::Blocks Forums

User forums => Nightly builds => Topic started by: killerbot on February 12, 2011, 05:31:34 pm

Title: The 12 February 2011 build (6992) is out.
Post by: killerbot on February 12, 2011, 05:31:34 pm
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.codeblocks.org/index.php/topic,3232.0.html).

A link to the unicode windows wxWidget dll for Code::Blocks : http://prdownload.berlios.de/codeblocks/wxmsw28u_gcc_cb_wx2810_gcc451-TDM.7z

For those who might need this one (when no MingW installed on your system) : the mingw10m.dll : http://prdownload.berlios.de/codeblocks/mingwm10_gcc451-TDM.7z

The 12 February 2011 build is out.
  - Windows :
   http://prdownload.berlios.de/codeblocks/CB_20110212_rev6992_win32.7z
  - Linux :
   none

Resolved Fixed:


Regressions/Confirmed/Annoying/Common bugs:


Title: Re: The 12 February 2011 build (6992) is out.
Post by: cacb on February 12, 2011, 08:33:22 pm
Resolved Fixed:
  • CC: fixed bug that global variables are left expanded in the project file (thanks oBFusCATed)

Great! I have been eagerly awaiting that fix. It has caused me some annoyance lately.

Thanks for your work.... downloading now.
Title: Re: The 12 February 2011 build (6992) is out.
Post by: Jenna on February 12, 2011, 09:04:23 pm
Debian packages (binaries and sources) for 32-bit and 64-bit systems can be found in my repo (http://apt.jenslody.de/).
Title: Re: The 12 February 2011 build (6992) is out.
Post by: Xaviou on February 12, 2011, 10:56:31 pm
Ubuntu 10.04+ Amd64 tar.gz archive (containing '.deb' installers builds with wx2810 from Ubuntu's official repository) can be found  here (http://www.archive-host.com/compteur.php?url=http://codeblocks.archive-host.com/CB_20110212_1005_rev6990_Ubuntu1004-1010_wx2810_amd64tar.gz) (direct link, rev 6990).

The "Tools+" menu entry is not shown if i18n is on.

Regards
Xav'
Title: Re: The 12 February 2011 build (6992) is out.
Post by: dmoore on February 12, 2011, 11:37:29 pm
The "Tools+" menu entry is not shown if i18n is on.

I just commited a fix to C::B trunk that included the accelerator in the FindMenu calls made by Tools+. Hopefully this will help. See here (http://developer.berlios.de/patch/?func=detailpatch&patch_id=3110&group_id=7745)
Title: Re: The 12 February 2011 build (6992) is out.
Post by: Phenom on February 13, 2011, 07:36:34 pm
Filemanager and Tools+ are the most useful plugins ever! Thanks for your great work.
Title: Re: The 12 February 2011 build (6992) is out.
Post by: oBFusCATed on February 13, 2011, 08:48:05 pm
The compiler plugin is way more useful  :lol:
Title: Re: The 12 February 2011 build (6992) is out.
Post by: oBFusCATed on February 13, 2011, 08:55:03 pm
dmoore: Is there a reason you're not adding stuff to the Tools menu, having two menus named identically is not good.
Title: Re: The 12 February 2011 build (6992) is out.
Post by: Xaviou on February 13, 2011, 09:25:12 pm
The "Tools+" menu entry is not shown if i18n is on.

I just commited a fix to C::B trunk that included the accelerator in the FindMenu calls made by Tools+. Hopefully this will help. See here (http://developer.berlios.de/patch/?func=detailpatch&patch_id=3110&group_id=7745)
It works, Thanks

Xav'
Title: Re: The 12 February 2011 build (6992) is out.
Post by: nanyu on February 14, 2011, 08:21:25 am
good job!

"...cycle through project manager -> editor -> "logs and others" via CTRL+ALT+TAB..."
but in win7, it is same as "Alt + Tab".. windows will hanld those key and show a swithcher panel.
Title: Re: The 12 February 2011 build (6992) is out.
Post by: daniloz on February 14, 2011, 08:56:26 am
"...cycle through project manager -> editor -> "logs and others" via CTRL+ALT+TAB..."
but in win7, it is same as "Alt + Tab".. windows will hanld those key and show a swithcher panel.
Same here in Vista, Ctrl+Alt+Tab shows the switcher panel... The difference from Alt+Tab is that when I release the Tab key, the panel stays and I can choose with the mouse the window I want to enable...

Known hotkey in Vista/win7 ???
Title: Re: The 12 February 2011 build (6992) is out.
Post by: nanyu on February 14, 2011, 02:41:01 pm
a bug make c::b crash.

1) open a workspace, and open some files.
2) click a main menu item
3) and move mouse over a menu item above, and let the mouse and also on a file TAB and above.
3) wait the hint window show.
4) wait a moment, or make mouse move away...

will see the c::b crash.

==========
win7 c::b svn 6992.

===========
addition : before c::b crash, it's window turn white.


Title: Re: The 12 February 2011 build (6992) is out.
Post by: MortenMacFly on February 14, 2011, 04:24:24 pm
Known hotkey in Vista/win7 ???
Mmmmmh. Good question. I didn't know this is an exis5ting hotkey in Vista+

What aout adding Shift in addition on these platforms? Or is there any other "common" one?
Title: Re: The 12 February 2011 build (6992) is out.
Post by: daniloz on February 14, 2011, 04:45:51 pm
What aout adding Shift in addition on these platforms? Or is there any other "common" one?
Shift-Alt-Tab is in use in Window, it's just Alt-Tab in reverse order....

But I think you meant Ctrl-Shift-Alt-Tab... I'm almost running out of fingers here... :D
Title: Re: The 12 February 2011 build (6992) is out.
Post by: stefanos_ on February 14, 2011, 04:51:23 pm
guys, the latest revision 7009 has an issue with code completion while typing header file name. I created an empty project to print "hello world" and seems that the parser locates only the C header files and not the C++.

System Specs:

OS: Windows XP SP3 Professional
Compiler: TDM's GCC 4.5.0
svn revision: 7009

When I will go home, I will test it on my Debian PC and I will let you know.
Title: Re: The 12 February 2011 build (6992) is out.
Post by: Phenom on February 14, 2011, 08:53:02 pm
Bug: I tried to delete an empty directory with FileManager, but I got the message "Could not open handle <path>" and CodeBlocks crashed.
Title: Re: The 12 February 2011 build (6992) is out.
Post by: mariocup on February 14, 2011, 11:39:42 pm
Hi,

I installed codeblocks revision 6996 from jenslody repository under ubuntu 10.10. If I disable the compiler plugin and then I open e.g. a cpp-file then codeblocks will crash.

I disabled quite a lot of plug-ins, but I think it is related to this plugin.

Regards,

Mario
Title: Re: The 12 February 2011 build (6992) is out.
Post by: Jenna on February 15, 2011, 06:45:24 am
Hi,

I installed codeblocks revision 6996 from jenslody repository under ubuntu 10.10. If I disable the compiler plugin and then I open e.g. a cpp-file then codeblocks will crash.

I disabled quite a lot of plug-ins, but I think it is related to this plugin.

Regards,

Mario

I only get (or gotit, will try again) if I remove (or rename) th ecompiler plugins library.

You might have seen, that I added debconf scripts to rename (and therefore not load) some of the plugins, except for the compiler plugin:
At the moment there is another (most likely more important) issue to look into:
If compiler-library is removed, you can not  open any files with "File->Open" or from recent file list, because C::B crashes immediately.
That's the cause, why I inhibit renaming of compiler pluzgin via debconf.

But it worked for me with a disabled plugin (from inside C::B).
I will try to investigate more.
Title: Re: The 12 February 2011 build (6992) is out.
Post by: Jenna on February 15, 2011, 07:33:50 am
Hi,

I installed codeblocks revision 6996 from jenslody repository under ubuntu 10.10. If I disable the compiler plugin and then I open e.g. a cpp-file then codeblocks will crash.

I disabled quite a lot of plug-ins, but I think it is related to this plugin.

Regards,

Mario

I only get (or gotit, will try again) if I remove (or rename) th ecompiler plugins library.

You might have seen, that I added debconf scripts to rename (and therefore not load) some of the plugins, except for the compiler plugin:
At the moment there is another (most likely more important) issue to look into:
If compiler-library is removed, you can not  open any files with "File->Open" or from recent file list, because C::B crashes immediately.
That's the cause, why I inhibit renaming of compiler pluzgin via debconf.

But it worked for me with a disabled plugin (from inside C::B).
I will try to investigate more.
I just tested it, and it crashes also.
The "funny" thing is, that it seems to shut down C::B, th bachtrace shows only some destructors, that have been called and C::B writes back a changed default.conf .
Title: Re: The 12 February 2011 build (6992) is out.
Post by: MortenMacFly on February 15, 2011, 07:55:01 am
I just tested it, and it crashes also.
Here, too. It seems the crash is traced back to CC -> nativeparser.cpp:645 where the requested compiler is invalid. This can happen (as we see) and should therefore be handeled differently.
Title: Re: The 12 February 2011 build (6992) is out.
Post by: MortenMacFly on February 15, 2011, 08:02:38 am
Here, too. It seems the crash is traced back to CC -> nativeparser.cpp:645 where the requested compiler is invalid. This can happen (as we see) and should therefore be handeled differently.
You The attached patch may resolve it (untested though).

As it "cbThrows" this explains why the default.conf still gets saved. That's a fail-safe option.
Title: Re: The 12 February 2011 build (6992) is out.
Post by: Jenna on February 15, 2011, 08:26:37 am
Here, too. It seems the crash is traced back to CC -> nativeparser.cpp:645 where the requested compiler is invalid. This can happen (as we see) and should therefore be handeled differently.
You The attached patch may resolve it (untested though).

As it "cbThrows" this explains why the default.conf still gets saved. That's a fail-safe option.
Fix confirmed on debian 64-bit, with disabled and removed compiler.
Title: Re: The 12 February 2011 build (6992) is out.
Post by: MortenMacFly on February 15, 2011, 09:26:06 am
Fix confirmed on debian 64-bit, with disabled and removed compiler.
Feel free to commit, I don't have SVN access atm (and probably for the next couple of days...).
Title: Re: The 12 February 2011 build (6992) is out.
Post by: Loaden on February 15, 2011, 12:53:42 pm
Fix confirmed on debian 64-bit, with disabled and removed compiler.
Feel free to commit, I don't have SVN access atm (and probably for the next couple of days...).
Thanks for quickly fixed!
Has been applied in the rev7010.
Title: Re: The 12 February 2011 build (6992) is out.
Post by: stefanos_ on February 18, 2011, 08:03:58 am
Guys, I don't know if it's a minor bug or not, but it seems that AStyle "violates" Code::Blocks's Coding Style (http://wiki.codeblocks.org/index.php?title=Coding_style).

To reproduce this:
create a new class name Foo
enter your curly braces; it will automatically indent your cursor by a tab / 4 spaces size (if i am correct; if not correct me please!)
Enter either public:, or private, or protected:, and see them left indenting like the Bad example from Coding Style.

I know that is a minor issue, but I am trying to adapt the Code::Blocks's Coding Style in my programming life :)

Cheers.
Title: Re: The 12 February 2011 build (6992) is out.
Post by: Folco on February 18, 2011, 09:39:27 am
Some people like that public/protected/private is aligned with {}. I think it's horrible. But this fact seems to be voluntary.
Title: Re: The 12 February 2011 build (6992) is out.
Post by: Loaden on February 18, 2011, 11:39:08 am
Guys, I don't know if it's a minor bug or not, but it seems that AStyle "violates" Code::Blocks's Coding Style (http://wiki.codeblocks.org/index.php?title=Coding_style).

To reproduce this:
create a new class name Foo
enter your curly braces; it will automatically indent your cursor by a tab / 4 spaces size (if i am correct; if not correct me please!)
Enter either public:, or private, or protected:, and see them left indenting like the Bad example from Coding Style.

I know that is a minor issue, but I am trying to adapt the Code::Blocks's Coding Style in my programming life :)

Cheers.
Settings > Editor > Editor settings > Indent options > Smart indent
Please does not checked this option.
Title: Re: The 12 February 2011 build (6992) is out.
Post by: dmoore on February 18, 2011, 06:00:37 pm
dmoore: Is there a reason you're not adding stuff to the Tools menu, having two menus named identically is not good.

To replace the tools menu, Goto Tools+ -> Configure Tools -> Plugin Settings, There's a checkbox to replace Tools with Tools+. Otherwise disable the plugin. Ideally Tools+ should offer same features as Tools + more. (This isn't true right now and your old tools won't be available in tools+)

I decided not to replace tools with tools+ by default for transparency purposes (to make it clear for first timers to the plugin that this is a separate feature). Before the next release, maybe the devs collectively decide to do something different.

Title: Re: The 12 February 2011 build (6992) is out.
Post by: dmoore on February 18, 2011, 06:03:04 pm
Bug: I tried to delete an empty directory with FileManager, but I got the message "Could not open handle <path>" and CodeBlocks crashed.

Thanks for the report.

What OS? (Assume windows) Was the directory deleted the root of the tree displayed in the FileManager or a subdirectory? Did the crash occur after clicking ok on the "Could not handle" message or before? Can you replicate consistently?

Title: Re: The 12 February 2011 build (6992) is out.
Post by: Phenom on February 18, 2011, 07:00:00 pm
Quote
What OS? (Assume windows)
Yes, windows/

Quote
Was the directory deleted the root of the tree displayed in the FileManager or a subdirectory?
Subdirectory.

Quote
Did the crash occur after clicking ok on the "Could not handle" message or before?
When the message is shown, if you click ok it becomes unresponisive. The same is if you wait a few senonds not clicking ok.

Quote
Can you replicate consistently?
Unfortunately not. Try something like this: move the all the files of a folder to its parent directory and then try delete the folder.
 
Title: Re: The 12 February 2011 build (6992) is out.
Post by: stefanos_ on February 19, 2011, 08:55:12 am
Guys, I don't know if it's a minor bug or not, but it seems that AStyle "violates" Code::Blocks's Coding Style (http://wiki.codeblocks.org/index.php?title=Coding_style).

To reproduce this:
create a new class name Foo
enter your curly braces; it will automatically indent your cursor by a tab / 4 spaces size (if i am correct; if not correct me please!)
Enter either public:, or private, or protected:, and see them left indenting like the Bad example from Coding Style.

I know that is a minor issue, but I am trying to adapt the Code::Blocks's Coding Style in my programming life :)

Cheers.
Settings > Editor > Editor settings > Indent options > Smart indent
Please does not checked this option.

Loaden, thanks buddy :) I have checked it and now another problem arises. Everytime I open curly braces, it does not move cursor by single tab / 4 spaces, and that is even more irritating than before :D.

Anyway, thanks for the effort; I will stick with the smart indent then :) I don't mind.

Cheers

stefanos_
Title: Re: The 12 February 2011 build (6992) is out.
Post by: cacb on February 19, 2011, 04:17:01 pm
I decided not to replace tools with tools+ by default for transparency purposes (to make it clear for first timers to the plugin that this is a separate feature). Before the next release, maybe the devs collectively decide to do something different.

That was a good decision. I decided to keep the Tools menu and instead remove the Tools+. It works better for me.

I don't think it is wise if a plugin completely replaces existing "core" functionality. At least that decision should be left to the user, and that is what you did. So no problem thus far.
Title: Re: The 12 February 2011 build (6992) is out.
Post by: oBFusCATed on February 19, 2011, 04:20:24 pm
If a user wants tool+, it can't remove tools...
Title: Re: The 12 February 2011 build (6992) is out.
Post by: dmoore on February 19, 2011, 04:59:32 pm
If a user wants tool+, it can't remove tools...

As I noted above, you can choose to hide the tools menu using Tools+->Configure tools->Plugin Settings->Replace Tools Menu with Tools plus
Title: Re: The 12 February 2011 build (6992) is out.
Post by: codeur on February 19, 2011, 09:49:00 pm
I decided not to replace tools with tools+ by default for transparency purposes (to make it clear for first timers to the plugin that this is a separate feature). Before the next release, maybe the devs collectively decide to do something different.

I am glad you kept the Tools menu. As Tools+ does not seem to yet cover the same functionality as Tools (in particular the various ways of launching standard shells, and I have not seen separators). That would have made impossible my current use of the Tools. I also like the simple appearance of the inbuilt Tools.

For now I have disabled Tools+ and kept Tools, but thanks for offering this new plugin. It could become quite useful when more mature.