Version: (using Devel) OS: Linux Installed from: Compiled sources KDevelop uses different working sets for the areas/perspectives. This means that the "Debug" area can have a different working set than the "Code" area. I don't like this and would like to have this feature removed or an option to disable it. Quite often, without me doing anything intentionally, I end up with the Debug and Code area having different working sets. This disrupts my workflow when trying to debug something quite a bit: I use the Code area to write my new code, then I discover a bug. I set a breakpoint in the code (I have that file open anyway, because I was working on that), then run the debugger ... and suddenly all my open files are closed, because the Debug area uses a different working set. I have to re-open the same files again. Also, KDevelop tends to create working sets on its own, it would be better if it only created working sets on explicit user action.
The discussion about this already happened and IIRC the result was that during a debug session usually files are opened that you step into or set additional breakpoints and these are not wanted in the code area as they often don't relate to the actual code you're writing. Hence we're creating a new workingset when switching to the debug area. I agree about the last point though, I also often end up with far more workingsets than I ever needed/wanted to open, so creating workingsets semi-automatically is probably needed.
The working-sets are not your problem, but rather the solution to your problem: When you're in the debug-area, it costs you exactly one click to open the same working-set as in the code area. From then on, the files are synchronized due to the same working sets. We need to find something intelligent to do when the user automatically switches into the debug-area. Maybe, the best thing to do is: Open all files that have a breakpoint set. And about the other problem, it would be better to open another bug report. We basically just need some system to decide what working-sets were created automatically, and delete those or put them into some trash bin.
> it costs you exactly one click to open the same working-set as in the code area. Thanks, good point, didn't really think of that. However, I think that doesn't have the same scroll positions etc as the other area. And it is one click... So yes, the basic problem is auto-creating of working sets, that shouldn't happen. On the other hand, I can see your argument for avoiding cases where stepping opens tons of new tabs, that indeed always annoyed me. So I don't have a real solution either, only the feeling that it could be better.
So the actual bug report is a wontfix, with a little sidenote regarding kdevelop automatically creating workingsets which should be in a separate report (if someone cares...)