The 16 June 2006 build is out.

[Pecan]

This happened to me when I had accidently stowed an old wxmsw26<x>_gcc_cb.dll up the PATH chain.

I deleted all wxWidgets and mingw dll's from the path, re-installed, the all went well.

sorry, I did not follow you. could you explain more? because if I make a clean install on school's computer, the problem still there. e.g. I choose 'open' or 'project->open', also when I choose the directory.
so, please give a detailed info. thanks veeeeeeeery much. :?

The best I can remember is:

I had a dll build of wxWidgets 2.4.2 sitting in c:/wxWidgets242/lib and a wxWidgets dll build in c:/wxWidgets262/lib.
The path had something like  c:\wxWidgets242\lib;c:\codeblocks\bin;c:\window;c:\windows\...blablabla;c:\beta\wxWidgets262\bin;

Somehow my codeblocks system was getting all balled up using the 2.4.2 dlls or the codeblocks2.4.2 dll's with my 2.6.2 build. I got one crash after another every time it attempted to use a system dialog.

I deleted all wxWidgets dll's and all codeblocks dll's I could find from my system. Removed 2.4.2 from the path. Removed codeblocks from the path; rebuilt wxWidgets 2.6.2. Then it all worked fine.

Just my experience. Thought it might help.

[orefa]

I was wondering why BYO is included in the regular distribution. I don't see any relation between games and a programming IDE.

Can plug-ins be downloadable add-ons like Firefox extensions? If so then a core set can be included but frills would be downloaded as needed and questions about them would go directly to their writer instead of the C::B developpers.

[MortenMacFly]

Can plug-ins be downloadable add-ons like Firefox extensions? If so then a core set can be included but frills would be downloaded as needed and questions about them would go directly to their writer instead of the C::B developpers.

This only applies to the nightlies which shall include all plugins on purpose -> for testing! I'd say the installer of a distribution will allow you to select which plugins you'd like to install. And (I guess you know already) you can disable plugin(s) you don't need/like. They remain disabled if you install a new nightly. You can even just delete the DLL of the plugin you don't like at all from the C::B folder it it's gone until you install it again...
With regards, Morten.

[orefa]

Cool. Thanks. 

[oz]

The best I can remember is:

I had a dll build of wxWidgets 2.4.2 sitting in c:/wxWidgets242/lib and a wxWidgets dll build in c:/wxWidgets262/lib.
The path had something like  c:\wxWidgets242\lib;c:\codeblocks\bin;c:\window;c:\windows\...blablabla;c:\beta\wxWidgets262\bin;

Somehow my codeblocks system was getting all balled up using the 2.4.2 dlls or the codeblocks2.4.2 dll's with my 2.6.2 build. I got one crash after another every time it attempted to use a system dialog.

I deleted all wxWidgets dll's and all codeblocks dll's I could find from my system. Removed 2.4.2 from the path. Removed codeblocks from the path; rebuilt wxWidgets 2.6.2. Then it all worked fine.

Just my experience. Thought it might help.

emm....clear, but it seems the different problem we have. it actually does not crash, just pop up a dialog box, I randomly click whatever I want :lol: 'Abort', 'Cancel' or 'Ignore', and the CB will works as normal after that, it will not generate a report either. Because when I am at school, I have to make the clean install every time, so...do not have your problem, but thanks anyway. Anyone has some idea on that?

[killerbot]

I was wondering why BYO is included in the regular distribution. I don't see any relation between games and a programming IDE.

Can plug-ins be downloadable add-ons like Firefox extensions? If so then a core set can be included but frills would be downloaded as needed and questions about them would go directly to their writer instead of the C::B developpers.

It is just for fun and it's a nice little plug-in.
If we should stick very closely to the main goal without a little diversion for fun ....

By the way i assume after you install linux or Windows xp you uninstall the games : what has minesweeper to do with an OS, or you hack the code of ms exell to remove the hidden flight simulator ;-)

ok, back to my half-lif 2 episode 1 plug-in for CB ... just kidding ;-)

[orefa]

hack the code of ms exell to remove the hidden flight simulator

Ha! I didn't even know about that, I've never used Excel. But it's no wonder MS software has a reputation for bloatware. It makes you wonder what other deadwood they stuff in their products. :?

[Ceniza]

Flight simulator? I only remember the famous "Hall of Tortured Souls" of Excel 95.

Anyway, having that game doesn't make any harm, does it?

[Code Medic]

hi..

some issues with kboard ... on win32 c:b buils 2577 (16th june 2006)
the key repeat rate is dramatically reduced .... i have my repeat rate set to max in the control pannel.
i tried with other applications like scite... they are all fine.

cheerio.

[orefa]

Anyway, having that game doesn't make any harm, does it?

No, not at the moment. But if the collection of available plug-ins grows like the collection of Firefox extensions for example then a selection may have to be made. Including everything available with the standard distribution can make it unnecessarily bloated with options users don't really need. Also core developpers may receive a lot of questions about software they didn't write. It's not a problem today but something that came to mind as I was reading problems that users were reporting on something that is not directly CB-related. A separation seems appropriate. It's not my decision of course.

[Game_Ender]

There is going to be an auto update/plug-in install system that uses the Internet.  So in the future Code::Blocks plug-ins will be handled like firefox extensions.  They won't be in the core repository, you will just tell CB to go and get that plug-in and it will install it.  I guess it will be a little like devpacks, which makes some sense considering Mandrav worked on DevC++. 

Of course for that to happen we have to make some sort of stable branch, kill bugs and freeze the sdk api so that plug-ins can be guaranteed to work with certain version of CB.