[Qt-creator] .prf handling, application palette, and performance concerns

[Daniel Teske]

> If this were a task tracker I'd be reporting this as three separate
> issues, but as this is just a mailing list I'll drop everything in at once.
>
> I've been using Qt Creator for a few days now and I must say I'm quite
> impressed. The .pro handling is excellent except for a couple of quirks
> that I'm fairly sure are just bugs. The only shortcoming I've
> encountered in this regard is that it doesn't follow the CONFIG variable
> to read in imported .prf files
We do actually read .prf files, e.g. the moc.prf is read, but it might very 
well be that we don't look for .prf files in the right locations. So how does 
your setup look like? And where does the .prf file reside.
And please report all bugs you find with our .pro file handling.

>  Maybe make
> it configurable if you want the default to be what the preview version
> is using.
Yeah we'll make it configurable. That hidden color changer was first actually 
a easter egg, but it turned out to be useful for Qt Creators development, 
because we often have multiple versions of QtCreator running.

> but at home I have a Duron 1.3GHz and it drops 15-25% of my keystrokes.
That shouldn't be. The most limiting factor to Qt Creators performance isn't 
actually the cpu, but the graphics cards driver. So it would be good to know 
which kind of graphics card and which driver you have.

> I suspect the performance
> hit may be coming from the code completion but there's currently no way
> to disable it to find out. (I also know some users who would like to
> disable code completion anyway.)
Well the C++-engine is in our view a fundamental part of the architecture. So 
a lot of stuff, like e.g. the F1 key depend on the C++-engine. We intend to 
build more features on top of the C++-engine. 

daniel