Use Cases for Working Areas
apaku at gmx.de
Tue Jun 10 10:33:48 UTC 2014
On Tue, Jun 10, 2014 at 8:12 AM, Kevin Funk <kfunk at kde.org> wrote:
> On Monday 09 June 2014 22:04:33 David Narvaez wrote:
> > On Sun, Jun 8, 2014 at 7:39 PM, Aleix Pol <aleixpol at kde.org> wrote:
> > > Well, we can discuss whether we want the Breakpoints toolview
> available by
> > > default then, or to appear whenever we add a breakpoint.
> > I am more worried about
> > http://mail.kde.org/pipermail/kdevelop/2012-April/017682.html, that is
> > really irritating and has no solution right now.
> > David E. Narvaez
> I have to agree, I find that very confusing as well. It really "breaks my
> workflow" when switching from code to debug and back. Is there anyone out
> there who actually finds that behaviour useful? What are the intended use-
IIRC the original motiviation for this behavior to avoid ending up with
tons of intermediate files that where visited during the stepping but do
not contain any bug.
Ideally that part could be kept, but I guess its hard/impossible for the
IDE to decide which files are important and which ones are not. And
requiring the use to 'tag' editors he wants to keep open is not really an
I would have suggested to use a single editor for stepping and when the
file changes load it into that editor and drop the previously-opened file,
but thats something that regularly annoys me in Eclipse. I often end up
looking at other parts than the direct caller in the original file and
hence dropping the editor and hence the cursor position I was at (would be
better if the cursor had been stored along with the file like vim does).
Just my 2 cents from my recollection of the history.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the KDevelop-devel