User forums > Help
Problems with Wx
Biplab:
--- Quote from: saddam le pion on March 02, 2007, 06:10:21 am ---You should also not abandon Dev-C++ but continue to use it in parallel with CB, because CB has still lots of bugs. The CB developpers that post here on the forum know so much CB, that they know how not to be bothered by the bugs. But we newcomer have not this knowledge.
--- End quote ---
Which bugs are bugging you? I can't agree with you that DevC++ doesn't have too many bugs. In C::B the code completion is not perfect, but it's far better that DevC++. I have used DevC++ for a long time and I'm well-aware how much buggy it's code-completion is. You press, Ctrl+Space in DevC++ and if you are lucky the options will come or otherwise it will give you a Crash-Report.
C::B devs develop C::B and thus they know C::B internals in details. Yes they also know the shortcomings. Another point is if you develop your own software, it's difficult to make it completely bug-free. Because creators often overlook the shortcomings of their creation. ;)
--- Quote from: saddam le pion on March 02, 2007, 06:10:21 am ---Some big projects i developped since 4 years with Dev-C++, i can't compile or link them with CB. Even if your project compile and link OK with CB, one day you may find a bug or a lack of feature in CB, that blocks further development of this project with CB.
--- End quote ---
I can't understand whether it's C::B's fault or you used wrong settings. Can you specify your problem in details? Also please specify which feature DevC++ has which C::B doesn't have? May be we can improve it in C::B. :)
--- Quote from: saddam le pion on March 02, 2007, 06:10:21 am ---What i realized also is 1) even at the beginning of using Dev-C++ it was easy to solve by myself most of the problem encountered (compile, link, interface use, etc...) 2) after downloading and using CB since nearly one year, i need this forum for solving most of the problems.
--- End quote ---
This can happen. DevC++ is hard coded for GCC whereas C::B supports a number of different compilers across different OS. So sometime to support everyone C::B devs need to stick to common minimum options. It's very difficult to satisfy each and every compiler in details.
In short, please be a bit specific about the difficulties you are facing. If possible put it in a different thread so that we can give you proper explanation or start improving the shortcomings. :)
Also please don't use vague terms to compare and show that C::B is not at par with other IDEs. If you love a software it's your choice but that doesn't mean alternatives are not good.
Regards,
Biplab
Game_Ender:
--- Quote from: saddam le pion on March 02, 2007, 06:10:21 am ---You should also not abandon Dev-C++ but continue to use it in parallel with CB, because CB has still lots of bugs. The CB developpers that post here on the forum know so much CB, that they know how not to be bothered by the bugs. But we newcomer have not this knowledge.
Some big projects i developped since 4 years with Dev-C++, i can't compile or link them with CB. Even if your project compile and link OK with CB, one day you may find a bug or a lack of feature in CB, that blocks further development of this project with CB.
What i realized also is 1) even at the beginning of using Dev-C++ it was easy to solve by myself most of the problem encountered (compile, link, interface use, etc...) 2) after downloading and using CB since nearly one year, i need this forum for solving most of the problems.
--- End quote ---
I am sorry, most of that is complete unsustantiated FUD. You really need to give some concrete example and problems before you go saying stuff like that. If you know how to compile things from scratch on the command line then you will have no trouble getting things to compile in CB. Any difficulties that you run into are almost certainly of you own making because CB is used by thousands of developers and the compilier plugin is the most used portion the IDE (hence least buggy).
Besides it seems like you ran into problems importing a Dev-Cpp project and getting it to work out of the box, that doesn't mean CB can't compile and link things correctly it means the importer needs to be fixed. Also you can't expect CB to work exactly like Dev-Cpp so you will need to spend some time learning the interface.
You also have not posted anything about the issues you mention on this forum. I did not check the patch/feature tracker but lets hope all of the issues with CB you mentioned have been reported there, so they can be fixed.
DarkDepths:
I wish that the files were not all so big. WxWidgets is 20mb, I have to redownload MingW, another 25mb. Im going to have to wait for awhile to download all this. Dial-Up is slowly killing me, I swear.
Oh, I do have another question though. In the cookbook wiki, it details building code::blocks. Is this nessecary, because I would much rather use a precomiled nightly or something.
Biplab:
I can understand problems with dial-up. You don't need to compile Code::Blocks. Please download Pre-Compiled Nightly from the following section of forum.
--- Quote ---http://forums.codeblocks.org/index.php/board,20.0.html
--- End quote ---
Latest nightly is available from the following thread.
--- Quote ---http://forums.codeblocks.org/index.php/topic,5320.0.html
--- End quote ---
Don't download the whole wxWidgets Package, download wxMSW package instead. You'll save some bandwidth. If you need compiled libraries of wxWidgets, I can upload one for you. :)
Regards,
Biplab
DarkDepths:
Well. I have already downloaded Wx. All I need now id MinGW. And great, I already have the latest nightly!
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version