Currently it's not possible to minimize the Recuva window as long the recover process is running.
That's annoying if you want to continue working. You can bring the Desktop to front, but as soon as you open another program/window, Recuva comes to the foreground again.
My suggestion: Adding a button "Send to background" (or something similiar) that minimizes Recuva.
It would be good then if the progress (%) would be displayed in the taskbar.
If you are trying to recover something from your computer it may not be a good idea to use it to do other things until the recovery is finished.
If you are trying to recover something from your computer it may not be a good idea to use it to do other things until the recovery is finished.
Yes, but usually if I recover something, it is from my USB stick or from a memory card.
I don't think, that e.g. browsing the internet would affect the recover process.
edit:
I think that Recuva should either hinder the user completely to work or allow him to minimize the program. Look at Defraggler: I don't think that it is wise to work intensively with the C drive while defragmenting it, but you can minimize Defraggler without any problems and continue working. So why not with Recuva?
I can picture crashes as a background worker. Besides if you are recovering you should not be using your machine. Less chance of recovery.
Perhaps if a user is recovering a pen drive or external hdd, and there are no active threads/processes depending on it, it'd be possible to lock the drive?
This would mean that a user could happily continue using the computer, without possibly effecting the recovery process.
e.g. I've just finished recovering data from a user with an external hard drive. It took 6 hours. He spent the rest of the day, working through his emails, and doing work that is in his My Documents.
From a system admin point of view, it would be really useful to lock access to the partition/drive being recovered. Most people are happy to not use the drive/pen whilst it is being recovered, or if they're too busy, just not have it recovered.
If a thread/process is sharing a drive/partition, it'd be really useful to have a list of which processes are preventing the drive from being locked, with a retry feature, that re-checks whether the drive can be locked, and if not re-generates the list, to show which processes are still using the drive.
Thanks,
Matthew