Use Cases for Working Areas
david.narvaez at computer.org
Fri Jun 13 18:52:45 UTC 2014
On Tue, Jun 10, 2014 at 6:33 AM, Andreas Pakulat <apaku at gmx.de> wrote:
> 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.
The current behavior keeps all intermediate files.
> 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 improvement
> 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).
I personally find some of these discussions about specific IDE
behaviors to be pointless because everybody tries to adapt the IDE to
their particular workflow. The difference between now and 2012 is that
back then you could manually change to the other area and see where
your debugging took you, and now you can't so there is no way to work
around the behavior (whether one likes it or not).
David E. Narvaez
More information about the KDevelop-devel