In Chronon 2.5, if you have a recording open in the debugger, then switch the perspective, go to manage recordings and delete all recordings (including the one just open in the debugger), you get an error message that your record is corrupt.
If you stop the debugger and try again deleting the records, everything works fine.
Maybe the "manage record" functionality should be aware of opened recordings.
[minor UI issue] Manage recordings -> delete conflicts with recording open in the debugger
EMPLOYEE0Prashant Deva (Official Rep) July 05, 2012 13:25added to buglist.
thanks for reporting this.
we will try to get a bugfix out today itself if we get an extra hour.Comment
EMPLOYEE0Prashant Deva (Official Rep) July 07, 2012 12:52ok turns out this is a little more complicated than we initially thought. if we put a lock file in the directory or the data structure representing that directory and for some reason the debugger crashes, it can lead to the user being unable to delete the recording at all unless doing so manually from the file system.
For this to work properly, every code path in the debugger will have to have checking to ensure that the 'lock' on the recording is taken off if any exception occurs.
Since the user not being able to delete a corrupt recording from the recording manager is a bigger issue than trying to delete a recording already in use (which most people wont do), we will leave this open for now and look at it later.