Community
Participate
Working Groups
When creating a new class, the New Class Wizard checks to see if it can find the header file containing the base classes on the project's include path. There are a couple of problems here. First, with per file scanner info, projects don't have include paths. But we can deal with that by creating fake files. But the real problem is that it's not taking into consideration Mac frameworks type include paths. The indexer is fine with it which is why it finds the base class. For example, QObject on my system comes from: /Users/dschaefer/Qt/5.5/clang_64/lib/QtCore.framework/Versions/5/Headers/qobject.h The include path that catches this is: /Users/dschaefer/Qt/5.5/clang_64/lib/QtCore.framework/Headers Somewhere in the parser it is determines that this is a framework and deals with it properly. Or, the new class wizard should just trust that the header file is on the include path. If it's in the index, it must be there...
