Re: [Qt-creator] Qt Creator 4.6 & editor messages

2018-04-10 Thread Nikolai Kosjar
Please file bug reports with these problems and your answers below. On 04/09/2018 05:17 PM, Andy wrote: Thanks Nikolai. 1) I obviously have a disconnect with the code model and includes somehow. I have no idea how to find that or fix it. I've played with the code model inspector but can't

Re: [Qt-creator] Qt Creator 4.6 & editor messages

2018-04-09 Thread Andy
Thanks Nikolai. 1) I obviously have a disconnect with the code model and includes somehow. I have no idea how to find that or fix it. I've played with the code model inspector but can't fix the issue. 2) The smallest example would be this lib that I forked a short while ago:

Re: [Qt-creator] Qt Creator 4.6 & editor messages

2018-04-04 Thread Nikolai Kosjar
On 29.03.2018 15:46, Andy wrote: It makes the editor very, very noisy to the point of being unusable. (And then there are the long pauses where I can't do anything & have to guess if it's going to come back to me or just hang - trying to isolate.) If all clazy and tidy checks are deactivated

Re: [Qt-creator] Qt Creator 4.6 & editor messages

2018-04-04 Thread Nikolai Kosjar
On 28.03.2018 20:58, Andy wrote: > When I get a message (warning/error) in the editor, how do I know which > it came from? Usually by looking at the diagnostic name / command line option that is also provided: For clazy, the diagnostics typically include "clazy" in the diagnostic command

Re: [Qt-creator] Qt Creator 4.6 & editor messages

2018-03-29 Thread Andy
Thanks for the suggestion Günter. No pre-compiled headers in the projects. I've also tried explicitly adding includes for things it's complaining about and it doesn't change anything. It could very well be something strange in the style of the projects I've tried (two of my own qmake-based, one

Re: [Qt-creator] Qt Creator 4.6 & editor messages

2018-03-29 Thread Andy
As a followup - even if I turn off clazy and tidy, I'm getting hundreds of "Semantic Issue" errors in the editor that are clearly not errors. A lot of "No member named 'foo' in 'bar'" and "Cannot initialize object parameter of type 'foo' with an expression of type 'bar'". It compiles cleanly