Hm...
I have found out that the plugin has problems while differing between two classes with the same class name but different namespaces. For example in my QT4 projects (I'm using the QT Designer tool for RAD) the designer tool produces code embedded into a namespace called Ui. Lets say the name of this embedded class is MainWindow, so its fully qualified name is Ui::MainWindow.
Naming my derived class with the same name MainWindow causes trouble with the plugin:
#include <qmainwindow>
#include "ui_mainwindow.h" // Produced by the designer tool
class MainWindow
: public QMainWindow,
public Ui::MainWindow
{
...
};
Now the plugin cannot differ between Ui::MainWindow and MainWindow accessings! Sure, I could rename my derived class and everything works fine, but in my opinion this behaviour is not very satisfying, isn't it?
@Kriz
I just wrote a simple test code, and every thing works fine.
class QMainWindow
{
int aaaa;
};
namespace Ui {
class MainWindow
{
int bbbb;
};
}
class MainWindow
: public QMainWindow,
public Ui::MainWindow
{
int cccc;
};
MainWindow x;
x.
Naming my derived class with the same name MainWindow causes trouble with the plugin:
So, What the exact problem you have with CC?
Can you describe it more specifically?
I do not have qt at hand, so I just test a simple vector code like:
#include <vector>
//using namespace std:
std::ve
then the screen shot shows it works fine.(latest cc_branch)
(http://i683.photobucket.com/albums/vv194/ollydbg_cb/2010-08-27075309.png)
note, I reopen(reparse) the project after I edit the code.( this means the #include <vector> should be there if you open the project, seems parsing in realtime does not add new headers to parser..).