I've also discovered a minor problem. I develop using dual screens. Code::Blocks correctly displays itself in my second screen, but when it displays dialog boxes it shows them in the other window, which is really annoying. One thing I did notice though, in some windows, e.g. project options, even though the dialog displays in the other window, when I click on the 'project build options...' within the dialog box the dialog box this opens, goes to the correct window.
1. How do I get the autocomplete/intellisense/class method list to be made available? I've compiled ok in mingw but still no context help is available
Check if Settings-->Environment-->View-->Enhanced multi-monitor dialog placement can solve your problemI don't have this option
Code completion is WIP. And a new one is in "development".I'm running the stable 1.0rc2, will getting the beta4 have these two options? I'm moving over because I'm sick of Dev-C++ crashing all the time and want to build MSVC and MinGW without running two IDE's, are the betas fairly stable?
#include "../../../axl_framework.h"Thanks, this new version is much, much nicer :)
However, I still don't get any help when typing 'object->' and I still get the same error with VS2003.
I don't know if I'm doing something wrong or whether it is meant to be like this, but when I switch compilers (between GCC and MSVC), it gets some of it's compiler/linker flags mixed up. For example, after minGW compiled ok, I switched to MSVC, enabled /MD flag, then when I switched back to minGW and tried to compile it failed saying '/MD no such file'. Even after removing the flag from MSVC, minGW gives me the same error and I can't compile minGW now.
While I'm here, I guess you could call this a feature request (unless it' been done), but when you switch compilers, it would be nice to get a completely new set of values in the build options, e.g. in minGW I reference a few .a files but when I switch to MSVC these are still there, similarly for MSVC, minGW settings shows a few .lib files.
Thanks.
Those compiler switches should not interfere with each other, so if that's the case, you have discovered a bug.
mandrav: I'm afraid neil is right - I can reproduce this issue. I've created a simple C++ console project, compiled with GCC, it's fine. Then in the "Build options" I changed the compiler to "MSVCToolkit" and enabled the /MD switch. C::B complained: "You have changed the compiler used for the project. Do you want to use the same compiler for all the project's build targets too?" and I said "Yes". I couldnt' compile (rebuild), but anyway. Then I switched back to GCC and tried to compile (rebuild) again. And look at the log:QuoteThose compiler switches should not interfere with each other, so if that's the case, you have discovered a bug.They don't interfere.
-------------- Build: default in Huhu ---------------
mingw32-g++.exe /MD -IE:\Devel\CodeBlocks\include -c main.cpp -o .objs\main.o
mingw32-g++.exe: /MD: No such file or directory
Process terminated with status 1 (0 minutes, 1 seconds)
0 errors, 0 warnings
any thoughts on why MSVC compiler is trying to use the profiled dll?
mandrav: I'm afraid neil is rightQuoteThose compiler switches should not interfere with each other, so if that's the case, you have discovered a bug.They don't interfere.
"Compiler options are not automatically converted when switching between compilers. This is a known limitation."Alright, got it. Sorry for the misunderstanding. :oops:
But I said it's not a bug but rather a known limitation.Well, if changing a setting in one compiler (/MD for MSVC) makes it impossible to compile for another (mingw) even if you subsequently turn off the flag (/MD for MSVC) then I would call that a bug.