automatic area switching

[David Nolden]

Am Donnerstag 25 Juni 2009 20:46:03 schrieb Niko Sams:
> On Thu, Jun 25, 2009 at 20:06, David Nolden
>
> <david.nolden.kdevelop at art-master.de> wrote:
> > Am Donnerstag 25 Juni 2009 19:19:05 schrieb Niko Sams:
> > > Why are documents part of the area?
> > > Imho this is not needed - we have the workingsets for that now.
> > > If I switch the area I want to debug/test the code I'm working on right
> > > now.
> >
> > It's part of the basic design, but with areas we can circumvent it. For
> > example, we could move or copy the current working-set into the debug
> > area when starting the debugger.
> >
> > The debugger can open tons of new documents during stepping, so it would
> > be good if there was an easy way of getting rid of those again. So I'd
> > propose that when starting the debug, we _copy_ the current working-set
> > into the debug area, but as a separate working set. Then you can switch
> > back into the code area, and have the clean working set from before.
>
> I like the idea that the areas and working sets are somehow connected but:
> - after every debug session one more working set is not good
> - the user should notice what's going on (magically duplicate areas)
>
> And the use case that you want to stop the debugger and hack right there
> won't work with this.

It would work because we wouldn't switch back automatically, but leave the 
option to the user. This could be a bit complicated though.

Another problem is, what happens to the working-set in the debug area when we 
start debugging? It probably shouldn't be overwritten.

So maybe we should only do it when there currently is no working-set in the 
debug area. Yes maybe we shouldn't copy it, but rather just move over the 
current one. The user still has the option to duplicate it if he likes.

Greetings, David