I've used both debuggers. It never occurred to me the difference of behavior.
But now that I notice, I think the OP is right, it definitely is preferred when
going through loops that fit on screen.
I see virtues of both approaches. But when equipped with a scroll wheel or area
on a track-pad the additional view management from ensureVisible() is not a
bother. I support the adding of an option, which I would probably use.
________________________________
From: Wiebe Cazemier <[email protected]>
To: Ziller Eike <[email protected]>
Cc: Qt Creator mailing list <[email protected]>
Sent: Monday, February 24, 2014 12:57 PM
Subject: Re: [Qt-creator] Not scroll editor when stepping in debugger
----- Original Message -----
> From: "Ziller Eike" <[email protected]>
> To: "Wiebe Cazemier" <[email protected]>
> Cc: "andre" <[email protected]>, "Qt Creator mailing list"
> <[email protected]>
> Sent: Monday, 24 February, 2014 9:38:03 AM
> Subject: Re: [Qt-creator] Not scroll editor when stepping in debugger
>
> In that case the editor shows all context of the currently executing line
> though (because all code in that file is visible).
> Br, Eike
True, but when the next statement would be in-screen, that would give you
enough context as well. IMO, there is no need for the current line to be
centered.
_______________________________________________
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
