Comment 4 for bug 1635408

Hi,

Okay, I shall do that in the next release.

Hamish

> On 27 Oct 2016, at 13:41, David <email address hidden> wrote:
>
> As far as I can tell, the whole disk was recovered. However, I could not
> see the summary results, showing how many errors there were and how much
> data was lost. This can be very useful information to give an idea how
> bad the disk was, and whether it is worth spending more time trying to
> recover it.
>
> Displaying the relevant information in that dialogue would certainly
> help.
>
> --
> You received this bug notification because you are a bug assignee.
> Matching subscriptions: hamishmb
> https://bugs.launchpad.net/bugs/1635408
>
> Title:
> End process not flexible
>
> Status in DDRescue-GUI:
> Triaged
>
> Bug description:
> Using 1.6.1 on OS X 10.6.8
>
> I have just finished recovering a disk with ddrescueGUI and it has
> done a brilliant job.
>
> However, I found the end process not very flexible. When it finished,
> it put up a dialogue saying all data had been recovered. Maybe this
> could be worded better because not all data was actually recovered. (I
> was thinking that was impressive!!)
>
> However, this dialogue box is modal, ie, it did not allow me to go to
> the main window to find out how much data had been recovered. :-(
>
> When I clicked Ok, up came another dialogue with three options: reset,
> mount and quit. The first would have obliterated the records of what
> had been done. The second I did not want to do because none of the
> filesystems were Mac native. And the third just quit the program.
>
> A simple solution here would be to make the dialogues non-modal so I
> could still interact with the main window.
>
> But I am not even sure that the dialogue is needed. The three options
> could easily appear in the main window or as menu items. Ideally, they
> would be greyed out until the recovery had finished.
>
> Another issue concerns saving the log file. It asked me if I wanted to
> save it. I said yes and it put up a dialogue asking for the name. I
> typed in a name and set the location, but after it finished, I could
> not find the file anywhere. It was rather weird asking for a file name
> to save the log since it has to be specified before starting.
>
> Anyway, just a couple of niggles in what was a fairly simple and
> successful process. Thanks.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ddrescue-gui/+bug/1635408/+subscriptions