Read hangs on read error

[David Perkins]

Using version 0.7, when I'm reading a flash card, and there is a read error, a popup is displayed showing the error. However, the read just hangs.
I'd like to be able to specify in the popup to either "ignore error and continue", or to "terminate operation".

[Tobin Davis (gruemaster)]

Will see what can be done. I believe the default action is to stop and return to the main window, leaving the operation terminated at the point of failure.

Part of the problem is that the Read operation is generic, and used to read either a file (in Write mode) or read a device (in Read mode), since the underlying dynamics of both operations are identical at that level (read from handle to buffer - handle being either the device or file).

In 99.9% of the cases, this error is fatal, but in the rare case of a device with a corrupt sector, I can understand the need to continue.

At this point it is too late to add to the v0.8 release (due hopefully in the next few days). I have one last major bug I will work on this weekend before releasing.

[Tobin Davis (gruemaster)]

I'm still on the fence on this one. The functions we use are from the Windows API and they usually chew you up and spit you out on any slight error. Will have to dedicate some time to experiment on this. No guarantees it will be in 1.0.