Code::Blocks

User forums => Nightly builds => Topic started by: killerbot on March 28, 2006, 06:15:01 pm

Title: The 28 march 2006 build is out.
Post by: killerbot on March 28, 2006, 06:15:01 pm
Get quick announcements through the RSS feed http://www.codeblocks.org/nightly/CodeBlock_RSS.xml
A link to the unicode windows wxWidget dll for Code::Blocks : http://download.berlios.de/codeblocks/wxmsw26u_gcc_cb.7z
For those who might need this one (when no MingW installed on your system) : the mingw10m.dll : http://download.berlios.de/codeblocks/mingwm10.7z

For support of ansi builds, a link to the ansi windows wxWidget dll for Code::Blocks : http://download.berlios.de/codeblocks/wxmsw26_gcc_cb.7z

The 28 March 2006 build is out.
  - Windows : http://download.berlios.de/codeblocks/CB_20060328_rev2272_win32.7z
  - Linux :
         http://download.berlios.de/codeblocks/CB_20060328_rev2272_ubuntu.deb
         http://download.berlios.de/codeblocks/CB_20060328_rev2272_fc4.rpm

Resolved Fixed:


Regressions/Confirmed/Annoying/Common bugs:


Title: Re: The 28 march 2006 build is out.
Post by: skirby on March 29, 2006, 12:05:03 am
Hello killerbot,

This release has a lot of interesting corrections.
I will test it as soon as possible.

Thanks a lot and have a nice day.
Title: Re: The 28 march 2006 build is out.
Post by: aguai on March 29, 2006, 05:06:10 pm
eh....
how to install

I cover the whole folder

then cant open....
Title: Re: The 28 march 2006 build is out.
Post by: Michael on March 29, 2006, 05:38:26 pm
eh....
how to install

I cover the whole folder

then cant open....

Sorry, but I have not fully understood your question/problems. Which are the errors/problems? What cannot open?

Best wishes,
Michael
Title: Re: The 28 march 2006 build is out.
Post by: sethjackson on March 29, 2006, 05:53:11 pm
Probably because he has no default.conf. C::B will not start up if you have no default.conf.

http://developer.berlios.de/bugs/?func=detailbug&bug_id=6829&group_id=5358

I can confirm with SVN revision from yesterday. Can't remeber which one it was......
Title: Re: The 28 march 2006 build is out.
Post by: TDragon on March 29, 2006, 06:00:16 pm
C::B will not start up if you have no default.conf.
I can't confirm this; this 28 March 2006 build starts up fine for me without a default.conf.
Title: Re: The 28 march 2006 build is out.
Post by: sethjackson on March 29, 2006, 08:41:53 pm
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
Title: Re: The 28 march 2006 build is out.
Post by: thomas on March 29, 2006, 08:49:57 pm
And what exactly does it fix?
Title: Re: The 28 march 2006 build is out.
Post by: sethjackson on March 29, 2006, 08:53:30 pm
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
Title: Re: The 28 march 2006 build is out.
Post by: thomas on March 29, 2006, 09:00:22 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....
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.
Title: Re: The 28 march 2006 build is out.
Post by: sethjackson on March 29, 2006, 09:03:44 pm
So why does removing the flag make the 99% CPU bug go away then?  :? I'm not trying to be argumentative just wondering...... Umm so what is my problem? Why can I not start C::B without default.conf?

EDIT:

This build works fine without default.conf.... Unfortunately my version compiled from SVN doesn't. :P
Title: Re: The 28 march 2006 build is out.
Post by: Pecan on March 29, 2006, 09:11:47 pm
So why does removing the flag make the 99% CPU bug go away then?  :? I'm not trying to be argumentative just wondering...... Umm so what is my problem? Why can I not start C::B without default.conf?

EDIT:

This build works fine without default.conf.... Unfortunately my version compiled from SVN doesn't. :P

I can confirm the 99% cpu bug is still present. I deleted my
*.conf, started CB. After choosing gcc at the compiler dlg, CB
went into a 99% cpu loop displaying the splash.
Title: Re: The 28 march 2006 build is out.
Post by: sethjackson on March 29, 2006, 09:14:13 pm
Thanks Pecan. At least I'm not alone in this big big world.  :lol: Anyways I wonder how to fix it??
If I download the nightly (this one), then delete my default.conf, the nightly runs fine. However, my SVN version doesn't.  :shock:
Title: Re: The 28 march 2006 build is out.
Post by: thomas on March 29, 2006, 09:24:35 pm
Well, look at app.cpp, line 575. Whatever is in that header, the default value is not used. Changing the default value in the header does not fix anything.

Yiannis was working on the startup problems yesterday afternoon, I thought he had fixed everything. Maybe there's more than one thing. Whatever it is, it is not the wxSTAY_ON_TOP flag, however. :)
Title: Re: The 28 march 2006 build is out.
Post by: Pecan on March 29, 2006, 09:26:54 pm
I can confirm the 99% cpu bug is still present. I deleted my
*.conf, started CB. After choosing gcc at the compiler dlg, CB
went into a 99% cpu loop displaying the splash.

However, clearing the STAY_ON_TOP flag did not solve the problem.

sorry
pecan
Title: Re: The 28 march 2006 build is out.
Post by: Ceniza on March 29, 2006, 09:40:03 pm
I still wonder if those bugs are my fault...

The current implementation of cbSplashScreen is really close, almost the same, to that of wxSplashScreen. The main difference is cbSS paints over the frame and wxSS uses an extra Window to draw.
Title: Re: The 28 march 2006 build is out.
Post by: thomas on March 29, 2006, 09:49:35 pm
It is not your fault, we had similar problems with wxSplashScreen before, but worked around them ;)
Title: Re: The 28 march 2006 build is out.
Post by: sethjackson on March 29, 2006, 09:58:11 pm
Well, look at app.cpp, line 575. Whatever is in that header, the default value is not used. Changing the default value in the header does not fix anything.

Yiannis was working on the startup problems yesterday afternoon, I thought he had fixed everything. Maybe there's more than one thing. Whatever it is, it is not the wxSTAY_ON_TOP flag, however. :)

Ok. Point taken. :D
Title: Re: The 28 march 2006 build is out.
Post by: Pecan on April 04, 2006, 05:51:11 am

This patch seems to have fixed the Splash loop on my XP
system with SVN 2290.

A statement in the wxWidgets book states that the paint
routine should always allocated a DC even if it doesn't do the paint.
This avoids a loop with the lib constantly calling the paint
routine.

I moved the DC allocation to the top of the routine so it was
allocated on every paint call and the hang went away.

Patch submitted.

Code: [Select]
Index: src/src/splashscreen.cpp
===================================================================
--- src/src/splashscreen.cpp (revision 2290)
+++ src/src/splashscreen.cpp (working copy)
@@ -22,12 +22,16 @@
 
 void cbSplashScreen::OnPaint(wxPaintEvent &)
 {
+    // an obscure statement in the wxWidgets book says to
+    // allocate the DC even if you don't paint to avoid
+    // a paint loop.    //pecan 2006/04/3
+  wxPaintDC paint_dc(this); //pecan 2006/04/3
   if (m_painted)
   {
     return;
   }
 
-  wxPaintDC paint_dc(this);
+  //-wxPaintDC paint_dc(this);
   DoPaint(paint_dc);
   m_painted = true; // paint once
 }

thanks
pecan
Title: Re: The 28 march 2006 build is out.
Post by: Ceniza on April 04, 2006, 03:59:19 pm
Good catch. I was even considering to remove the "paint once" thingy from there.

I'll modify my SVN copy to reflect that so it can be updated from there.

Thanks :)