Just for completeness, the main problem we have identified comes from the 
interaction of two things:

1) the cpp code model playing it safe and reindexing *everything* when the 
profile changes (because compiler flags could have changed.

2) directories in the .pro file (instead of plain files), making it easy to 
trigger a "change" of the project (just create a new file, autosave, or save in 
that directory).

We fixed the worst issues, and we plan a full fix for 3.0 (making the Cpp code 
model less aggressive in reindexing everything by checking more carefully if 
that is really needed).
Hopefully our at interim fixes solves your issues acceptably in the meantime.

Fawzi
On 3 Jul 2013, at 10:47, Ziller Eike <[email protected]> wrote:

> The snapshots on 
> http://download.qt-project.org/snapshots/qtcreator/2.8.0/2013-07-03-775/
> contain two fixes to related issues that we identified. Can you please all 
> check out if this build resolves your problem?
> 
> Br, Eike
> 
> On 28.06.2013, at 15:32, Nikolai Kosjar <[email protected]> wrote:
> 
>> On 06/28/2013 03:26 PM, Guido Seifert wrote:
>>> Unfortunately I can confirm this behavior.
>> 
>> Let's track this here:
>> 
>>      https://bugreports.qt-project.org/browse/QTCREATORBUG-9693
>> 
>> Nikolai
>> 
>> 
>> _______________________________________________
>> Qt-creator mailing list
>> [email protected]
>> http://lists.qt-project.org/mailman/listinfo/qt-creator
> 
> -- 
> Eike Ziller, Senior Software Engineer - Digia, Qt
> 
> Digia Germany GmbH, Rudower Chaussee 13, D-12489 Berlin
> Geschäftsführer: Mika Pälsi, Juha Varelius, Anja Wasenius
> Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, 
> HRB 144331 B
> 
> _______________________________________________
> Qt-creator mailing list
> [email protected]
> http://lists.qt-project.org/mailman/listinfo/qt-creator

_______________________________________________
Qt-creator mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/qt-creator

Reply via email to