Bug 287052

Summary: View is closed without asking for saving changes when two areas use the same workingset
Product: [Developer tools] kdevplatform Reporter: Niko Sams <niko.sams>
Component: editor integrationAssignee: kdevelop-bugs-null
Status: CONFIRMED ---    
Severity: normal    
Priority: NOR    
Version First Reported In: git master   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Niko Sams 2011-11-20 09:20:31 UTC 
This issue was initially reported by Leon Pollak.

Steps to reproduce:
1. close all open files in all areas
2. go to code area
3. open a file (a workingset is created)
4. switch to debug area
5. open the workingset used in code area (click the workingset icon from code area)
6. the same file will get opened in debug area
7. edit file (don't save!)
8. close file
9. file is closed, no question about saving is asked
10. whoops the file is also closed in code area - as the areas share the workingset
11. -> changes are LOST
thankfully Kates Data Recovery steps in and restores our changes.


Behaviour (not buggy) when using two independent workingsets:
1. close all open files in all areas
2. go to code area
3. open a file
4. switch to debug area
5. open the same file (a *new* workingset is created)
6. edit file (don't save!)
7. close the file
8. file is closed, no question about saving is asked
9. file is still open in code workingset, including the unsaved change
I guess this is expected behaviour.
Comment 1 Justin Zobel 2021-03-09 23:43:38 UTC 
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.