User forums > Nightly builds

The 28 march 2006 build is out.

<< < (2/4) > >>

TDragon:

--- Quote from: sethjackson on March 29, 2006, 05:53:11 pm ---C::B will not start up if you have no default.conf.

--- End quote ---
I can't confirm this; this 28 March 2006 build starts up fine for me without a default.conf.

sethjackson:
I have it with Version 1.0 revision 2274 (gcc 3.4.4 Windows/unicode, build: Mar 28 2006 14:05:04). :P

Fix is here.

http://developer.berlios.de/patch/index.php?func=detailpatch&patch_id=969&group_id=5358

thomas:
And what exactly does it fix?

sethjackson:
The bug that you can't open C::B with no default.conf (C::B uses 99% CPU).

Ok patch was rejected. BUT I removed it from that header and it works perfectly. If that flag was in the header C::B use 99% CPU if I have no default.conf....

EDIT:

See here. I have the same problem AGAIN.

http://forums.codeblocks.org/index.php?topic=2608.msg20648#msg20648

thomas:

--- Quote from: sethjackson on March 29, 2006, 08:53:30 pm ---Ok patch was rejected. BUT I removed it from that header and it works perfectly. If that flag was in the header C::B use 99% CPU if I have no default.conf....
--- End quote ---
I originally removed that flag from the header, but left it there when updating to Ceniza's newest release of the splash screen class. It is a default parameter, so it was trivial to specify the correct parameter in app.cpp. This way, we do not have a patched 3rd party component (which would cause problems every time we update it, again). We need not and we should not patch that header.

The flag is, however, not related to the 99% CPU bug (this one was fixed by Yiannis independently). The flag was related to the message box lockout and later to the update event crash.

Navigation

[0] Message Index

[#] Next page

[*] Previous page