I 've had the same problems as you did. For now I 'm settled with Eclipse for my general programming tasks but I 'm not 100% happy with it. I use Code::Blocks for all my Qt related projects (I have even set up a plugin for doing so QtWorkbench) and that's what I voted on your poll. I would say that your needs will be partially satisfied by Code::Blocks. This is because everything there is build around the project base path so if you prepare typical .pro files (with SUBDIRS and stuff) you 'll lose the (most importantly) debugging facilities and all the other features that depend on the working directory during builds. My usage is as follows:
* Generate my project with Code::Blocks
* Let my plugin generate Code::Blocks "friendly" .pro files
* I "turn on" code completion for Qt classes (works quite well and this is for me the strong point against Eclipse)
* Code, Build blah blah using Code::BLocks (which IMHO is a pretty good IDE)
* By the time I have to release something I handwrite my .pro files and test them using the command line.
Bookmarks