[Qt-creator] Qt-Creator Feature Requests

[Andre Poenitz]

On Tue, Nov 04, 2008 at 03:00:44PM +0100, Michael Sué wrote:
> Hi QtCreator Team,
> 
> it's great! I found something to improve, though :)

That's a surprise ;-)
 
> I'm working on Linux Fedora Core 8; using Qt 4.4.2.
> 
> 1) I have to delete and reset the breakpoints after any recompilation of the
> code surrounding the breakpoints. This is ennerving, and I "always" forget
> it.

In theory the breakpoints should be re-set when restarting the
debugging. It is strange that this should not work, but adding them
"maniually" does. Could you select Debug mode, go to the drop down
menu named "View" in the lower right corner of the main editor area,
uncheck the "Locked" entry, switch on the "Gdb" view, and send me the 
output of both panels?

> 2) If the Debugger stops at a breakpoint the debugger should raise in front
> of the application on its own. I'm using the Linux-machine from a WINDOWS
> machine via Putty, so maybe it's a Putty problem.

Raising the application triggers all kinds of fancy events which have 
a high potential to interfere with the issue one wants to examine. So
an unconditional "Raise" does not sound right. We should think about
less intrusive options... flashing the taskbart or such perhaps, or
a toggle somewhere...

> [...]

> Debugging is a bit slow (about one second per simple line of
> code on a Sun Fire X2200 M2 which (at this moment) has nothing else to
> do), but still it's great to have it !

You could switch of the "Custom Displays for Qt Objects", but other than
that there should be not much overhead on top of what gdb requires. Is
debugging using "plain" gdb faster than what you see in Qt Creator?

Andre'