[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:       Andreas Pakulat <apaku () gmx ! de>
Date:       2010-03-29 20:05:13
Message-ID: 20100329200513.A9AEA3C0C8 () immanuel ! kde ! org
[Download RAW message or body]

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





--- Comment #7 from Andreas Pakulat <apaku gmx de>  2010-03-29 22:05:06 ---
(In reply to comment #6)
> (In reply to comment #4)
> > 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?

Hmm, I must have misremembered that then. It indeed works like that.

> > > 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.

No, my problem with it is that certain toolviews (in particular the GDB and
Breakpoints tab) are gone when it switches back. And that the currently visible
view (no split-views here) is not "shared" between the areas.

> > > 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)

Yeah, that would work. However I actually just tried that and when I switched
to debug and opened a file I got a workingset. And apparently the same
workingset was created in code-area (I got an icon and it has the same files
there).

So either this got already fixed after Beta9, or the OP indeed did something
different. Maybe his working set was from the time when the two area's didn't
share it?

-- 
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]