Unfortunately it's not possible because my code is c++14/17 heavy and old parser just doesn't work with it. If it was an option, I would have done it long ago.
On Sat, Jan 5, 2019 at 6:04 AM Sze Howe Koh <szehowe....@gmail.com> wrote: > On Sat, 5 Jan 2019 at 09:26, NIkolai Marchenko <enmarantis...@gmail.com> > wrote: > > > > Qt creator is rapidly becoming a source of major annoyance ever since > clang code model was introduced. > > > > It's slow, sometimes taking 30+ seconds to react to F2 > > What's worse, it reacts to it once you gave up and navigated somewhere > manually and makes you suddenly type stuff in plces you won't expect. > > > > It's buggy, fails on boost and fails to produce a highlight on > everything that depends on it > > > > It's too easy to break, A single symbol it doesn't detect breaks > highlighting and hint for the whole file chain, whether stuff later down > the line requires that symbol or not. > > > > While I understand the desire to stop reimplementing the wheel with code > parser, the Clang Code Model made Qt Creator strictly worse for any complex > project to the point I catch myself wanting to use something else on a > regular basis. This wasn't the case ever before CCM was introduced. > > Revert to the old code model by disabling the Clang code model in the > Plugins dialog (on Windows, it's "Help > About Plugins... > C++ > > ClangCodeModel") > > > Regards, > Sze-Howe >
_______________________________________________ Qt-creator mailing list Qt-creator@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
