Closing database does not always remove file locking #13
Description
This is most obvious when code is run in a batch script, which creates multiple database hdf5 files. All created files, except for the first one, stay locked, even though the file handles should have been released.
This issue appeared after adding the 1D rocking scan integration, which has another database (hdftreeview) widget. My best guess is that the second widget somehow leads to the creation of multiple locks, which are not properly released. In a batch script, the main qt thread is occupied most of the time and signals and events might not be processed in the correct order.