Imagesleuth - Another Retroreveal Replacement

Some sort of status indicator would probably be a good idea, as I imagine the processing times will vary considerably depending on machine specs, but also possibly the image type and resolution.

In comparison to Don's numbers above, I inadvertently dragged a 3.25MB jpeg image into the window (2900 x 2800 pixels) and thought I might have to manually kill the application, but it completed processing in about 20 seconds, sooner than I expected. (Windows 10 Pro, i7-6700k, 64GB RAM)

Suggestion to both guard against runaway processing yet allow some flexibility by the user:

In settings have maximum image dimension fields (W x H), and if the image uploaded or dragged exceeds those dimensions, do not process but instead display a warning that the image dimensions exceed allowable maximum. Set the default to something like 1000x1000, but allow the user to specify a larger maximum.

This sets a reasonable maximum yet allows those with more capable machines and/or higher needs to ramp up the capabilities of the software.

Something strange is going on, perhaps it is me...

After an app restart, the app now seems to be performing better, with 1.5MB files being processed in about 20 seconds. In looking at Windows Task manager, the app is only consuming about 17% CPU and 1.6MB of RAM (memory usage reflects size of image file).

The only thing that changed was that I resized the app window, is it possible that the app was struggling with an odd sized window?

So I have been testing with different windows sizes but now cannot seem to replicate the slow 1MB times I was previously seeing. Perhaps some neutrino that passed through the PC hosed it until I restarted the app...

FYI, Windows Task Manager shows the app as being 'Not Responding' while it is processing.
Don

Don and revenuecollector,
Thank you very much for the very helpful feedback.

One idea I am thinking of is to have the screen update periodically while processing the image. This will display thumbnails in groups rather than waiting until they have all have been generated as currently happens.
This would provide both ongoing visual feedback and will also allow system events to occur allowing other applications such as Explorer to continue to respond.

I like the idea of having a user-configured maximum image size, a 1000x1000 default seems like a good starting point. Along with this, I am thinking that it could also be worthwhile to give the user the option of automatically scaling down larger images prior to processing.

The size of the application window should have a negligible effect on display time.

Thanks,
Clive