[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 232566] pressing escape in debug mode switches to code tab and
From:       Niko Sams <niko.sams () gmail ! com>
Date:       2010-03-29 19:39:44
Message-ID: 20100329193944.AD9E03C088 () immanuel ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=232566





--- Comment #6 from Niko Sams <niko sams gmail com>  2010-03-29 21:39:43 ---
(In reply to comment #4)
> (In reply to comment #3)
> > Debug area is activated automatically when a debug session is started. The
> > currently open workingset is opened in the debug area too, so Code and Debug
> > area have the *same* workingset. Unless you create a new workingset the
> > workingset should be kept wen switching back to code area.
> 
> Thats not exactly true, as the workingset in debug area is a copy opening files
> in debug area doesn't automatically open files in the code area. 
It's not a copy, it's the same workingset. When opening a file in debug area
and switching back to code area it stays open. Or do I misunderstand you?

> > Automatic switching back happens when the debug session ended. (note that ended
> > != stopped)
> 
> Can we have an option for that or even disable it always? I know I suggested to
> do that, but after having used it a bit now it is more annoying than useful -
> IMHO.
We can think about removing the automatic switch again - configuration is not
neccessary imho.
What annoys you about it? Maybe we can fix that. 
If workingsets would store & restore correctly:
- tab order
- active file
- view scroll position and cursor position
it should not be annoying.

> 
> > Ok - that's how it should be. Now could you post more information on how to
> > reproduce the issue (and take an eye on the workingsets)
> 
> That should be easy: Start kdevelop with a fresh session. Go to debug area,
> start opening files to work on them. Then configure a launch and start to debug
> it. Now hit ESC to cancel the debugging and you're automatically taken back to
> code area with an empty workingset.
Ah, I see. Can this be fixed by opening the workingset that is active in debug
area in code area when automatically switching to it? (As it does when
switching the other way)

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

_______________________________________________
KDevelop-bugs mailing list
KDevelop-bugs@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-bugs
[prev in list] [next in list] [prev in thread] [next in thread]