pkumar wrote:Hi Daniel,
I use code::blocks too - an old version(12.11) on win 7. I tried a recent version(16.01). While compiling, the display goes haywire - then recovers. I did not understand why. After this happened several times I went back to the old version. Which is your version and have you faced any such problem?
Regards
Hello
I think I use a recent version and these things didn't happened for me . This evening I'll say to you the exact version I use , I'm not at home.(show a screen shot of your problem if you can).
But I remember I leaved the 12 .xx version because I never made the profiling plug in working properly.
Best
pkumar wrote:Hi Daniel,
I use code::blocks too - an old version(12.11) on win 7. I tried a recent version(16.01). While compiling, the display goes haywire - then recovers. I did not understand why. After this happened several times I went back to the old version. Which is your version and have you faced any such problem?
jdart wrote:What is this IDE you speak of? All you need is a terminal and emacs.
I have had no special problem with VC++ but I am not using C#.
--Jon
I like code::blocks on Ubuntu.
Using Visual Studio has made me lazy
Using Visual Studio has made me go much faster than any other alternative, starting from vi, pascal, delphi... Why have to do strange things instead of just producing? I'm not interested on doing things by hand.
I'm just using Notepad++, also professionally. Sometimes, the only kind of "debugger" available is an oscilloscope, attached to some I/O pin of the microcontroller. In very difficult cases, not even that because it alters the timing. Then it's the Chuck Norris way - staring at the code and forcing it to confess.
I installed CB 16.01 again. There was no difficulty in rebuilding a project a few times. So I shall continue with this till the problem reappears. It may be relevant that my laptop has 4 GB of memory and quite a few other windows were open when CB crashed.
Out of curiosity,
I download Alfil 15.8 which is known to be a Stockfish derivative in C#, load it with your own project and compile it without an error.
I also had to disable the option "Enable diagnostic tool while debugging" otherwise debugging Skipper interface was really terrible slow.
Reminded me of doing a database exercise thirty years ago with twenty students working simultaneously.
By the way something is more going on. Perhaps downloading updates. For after 22:00 computer is much faster.
They just want you to buy a faster computer. Or they assume you work with best hardware. Probably all these software development tools are not well tested. They are just using us to test their software with these free downloads.