|Title||»||Use different strategy when we detect slow loading of Thermo files over the network|
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.