[BUG/FEAT.REQ.?] disable/gray out 'Repair' button when there's nothing to repair

[GerHobbelt]

MultiPar 1.1.9.5 always shows the Repair button active, even when it says there's nothing to repair (after a verification).
QuickPar provides a better 'user experience' on this detail, as it will grey out (keep disabled) the Repair button when it finds there's nothing to do (like renaming files and/or repairing the set using the par files)

Kudos for MultiPar so far, BTW!


P.S. I decided to post this in the forum as I couldn't find a bug tracker for MultiPar; seems others have done the same, but if there is a bug tracker, please point me to it as my google fu didn't deliver there.

[Yutaka Sawada]

from GerHobbelt

MultiPar 1.1.9.5 always shows the Repair button active, even when it says there's nothing to repair (after a verification).

 You seems to be a QuickPar user and switch to MultiPar recently. The behavior is intended in MultiPar GUI by a historic reason; there were two buttons "Verify" and "Repair" at very old versions. When "Verify" button was removed, "Repair" button needed to be always active to re-verify again. At that time, there was no short-cut key, and "Repair" had a same usage as "Verify" button. Now because GUI has "F5-key" to re-verify again, users don't need to push "Repair" button to re-verify.

 Though I just leave the old action in MultiPar GUI, it looks odd for QuickPar users. I will change the behavior to be same as QuickPar in next version. That may be easy to understand.

I couldn't find a bug tracker for MultiPar

 This forum is good to public a bug/problem/request. Other users can know what is known incident and is being fixed/implemented. Sometimes when the bug is very complex or hard to test on my PC, I ask the poster to send the report(screen-shot, log, etc) by mail. Then, I will send him a sample version for confimation or test.

[GerHobbelt]

You seems to be a QuickPar user and switch to MultiPar recently.

Yes, spot on! :-)
Read some rumours about MultiPar being faster on multi-core boxes compared to QuickPar, so I had to see this for myself. Looking good so far!

Though I just leave the old action in MultiPar GUI, it looks odd for QuickPar users. I will change the behavior to be same as QuickPar in next version. That may be easy to understand.

This forum is good to public a bug/problem/request. Other users can know what is known incident and is being fixed/implemented. Sometimes when the bug is very complex or hard to test on my PC, I ask the poster to send the report(screen-shot, log, etc) by mail. Then, I will send him a sample version for confirmation or test.

Thanks, I'll be watching the updates and when there's anything to report, I'll post it in the forum as I did with this one.

Thanks for all your hard work on this; it's much appreciated.