Issue 393: Use different strategy when we detect slow loading of Thermo files over the network

issues
Status:closed
Assigned To:Guest
Type:Defect
Area:Skyline
Priority:4
Milestone:3.1
Opened:2015-01-14 by donmarsh
Changed:2016-07-27 by Brendan MacLean
Resolved:2016-07-27 by Brendan MacLean
Resolution:Fixed
Closed:2016-07-27 by Brendan MacLean
2015-01-14 donmarsh
Title»Use different strategy when we detect slow loading of Thermo files over the network
Assigned To»donmarsh@proteinms.net
Type»Defect
Area»Skyline
Priority»3
Milestone»3.1
When we detect slow loading of a Thermo file over the network, we quietly abort the load, copy the file to a local temp file, and then load that file from disk. This is not ideal for two reasons:

1. It has to be repeated for each data file, so the total load time is greater than if we copied all the files at once.
2. The user is never aware of what is happening. They don't get an opportunity to learn about the problem or change their behavior. They may feel that Skyline is just slow, and why is their disk drive filling up?

I think a better option would be to display a dialog when we detect the problem. We can inform the user what is happening, and give them a choice of continuing with this slow load (maybe they feel they don't have enough disk space to do a local copy), or copy the files to a directory of their choice, or just aborting the whole thing.

Brendan agrees this would be a better strategy.

2015-06-24 Brendan MacLean
Priority3»4
This issue has become a lot less likely with modern system software. So, I am downgrading the priority.

2016-07-27 Brendan MacLean
resolve as Fixed
Statusopen»resolved
We now just notify the user in the new UI.

2016-07-27 Brendan MacLean
close
Statusresolved»closed
Assigned Todonmarsh@proteinms.net»Guest