Refresh Column when hashes are involved needs work
Posted: 02 Aug 2022 04:16
v 23.40 (lifetime), Windows 11
This started within the last few months, but Refresh Column causes the program to go unresponsive for long periods of time when computing hashes on long lists of large files. I used to be able to copy partial results to the clipboard while the operation was ongoing to reduce the chance of losing hours of work, but that's become very difficult to do reliably, as I now have to time it just right. Also, if I'm doing this on search results, switching away from the tab loses all the work, which is a big reason I learned to save partial results. Finally, pressing Esc to abort the operation causes the window to immediately go white and the title bar to display (Not Responding), which lasts for many seconds if done on, say, a 4 GB file, and when the window returns to the normal color, "refreshing column... (ESC to stop)" is still displayed, it appears it's moved on to the next large file, and pressing Esc has the same effect. I just endured this for a test setup of four files, and at the end, the MD5's were displayed for all four; IOW, there's no way to abort the operation, except maybe to time switching to another tab just right.
To begin fixing these problems, Refresh Column could be moved to a separate thread, and any interruption of that thread should be prompted. Potentially lengthy individual file operations like hash computation would have to threaded as well or at least cooperatively multitasked. It would also be nice if the MD5 column was filled in as results are computed. It used to be that I could drag the scroll bar while the operation was ongoing, and the ones that had been computed would be displayed when brought into view, but this new unresponsiveness prevents even this.
This started within the last few months, but Refresh Column causes the program to go unresponsive for long periods of time when computing hashes on long lists of large files. I used to be able to copy partial results to the clipboard while the operation was ongoing to reduce the chance of losing hours of work, but that's become very difficult to do reliably, as I now have to time it just right. Also, if I'm doing this on search results, switching away from the tab loses all the work, which is a big reason I learned to save partial results. Finally, pressing Esc to abort the operation causes the window to immediately go white and the title bar to display (Not Responding), which lasts for many seconds if done on, say, a 4 GB file, and when the window returns to the normal color, "refreshing column... (ESC to stop)" is still displayed, it appears it's moved on to the next large file, and pressing Esc has the same effect. I just endured this for a test setup of four files, and at the end, the MD5's were displayed for all four; IOW, there's no way to abort the operation, except maybe to time switching to another tab just right.
To begin fixing these problems, Refresh Column could be moved to a separate thread, and any interruption of that thread should be prompted. Potentially lengthy individual file operations like hash computation would have to threaded as well or at least cooperatively multitasked. It would also be nice if the MD5 column was filled in as results are computed. It used to be that I could drag the scroll bar while the operation was ongoing, and the ones that had been computed would be displayed when brought into view, but this new unresponsiveness prevents even this.