#17 Feature requests

open
Peter C
5
2003-08-24
2003-08-23
Clark Kent
No

I am currently using QuickPAR version .60

1) I would like to be able to resize the "auto-repair"
window so that I can see more file names on the screen
at one time. Currently you can see a maximum of 8
files on the screen (without using the scroll bar). I
would like to be able to see at LEAST 15 file names on
the screen.

2) I would like to be able to set "Auto Repair" as the
default and not have to click on it.

3) After the "Auto Repair" process has completed, under
the "Status" column, for any file(s) that have been
repaired, the "Status" should read "Repaired" and not
"Found" as it does now. If you put "Found" next to
each file AFTER the Auto-Repair process has run then we
have absolutely no idea which files have actually been
repaired (of course I know I can write them down on a
piece of paper after the "Verify" process, but I don't
want to write them down every time). It's very
important to me to know which file(s) were repaired
after the repair process. Actually "Found" is
misleading. Instead of "Found" you should use the word
"Complete" and any file(s) that were repaired after the
Auto-Repair process has run should read "Repaired".

4) This one isn't as important and maybe there's
nothing you can do to fix this but, if a file is
completely missing from the set and I do an
"Auto-Repair", QuickPAR is incredibly CPU intensive!!
I have a Pentium 800Mhz with 512MB of RAM (Windows
2000) and am getting about 67 MB/second with QuickPAR,
however, if a file that is approximately 10 MB large is
missing from the set then it takes QuickPAR about 4
minutes to recover that 10 MB file!! It takes the
SmartPAR program only about 15 seconds.

Thanks, and keep up the great work!

Discussion

  • Peter C

    Peter C - 2003-08-23

    Logged In: YES
    user_id=477089

    1) You can already resize the verification window. Just drag
    the top or bottom edges as you would in any other
    application. If this is not working for you, then you should
    submit a bug report.

    2) This is already in the list of requested features but has not
    yet been implemented.

    3) Found/Complete: This is a good suggestion and I will make
    the change. Complete/Repaired: This is reasonable request,
    and I will see if I can do it.

    4) The more data that needs to be repaired the more
    processing is involved. Repair (using par2) is inherantly CPU
    intensive and can take a long time on older CPUs. NB on
    UseNet it is rare for a file to be completely missing. To get
    the best use out of any PAR2 program you must download
    incomplete files.

     
  • Peter C

    Peter C - 2003-08-23
    • labels: --> Feature Request
    • assigned_to: nobody --> peterbclements
    • status: open --> pending
     
  • Clark Kent

    Clark Kent - 2003-08-24
    • status: pending --> open
     
  • Clark Kent

    Clark Kent - 2003-08-24

    Logged In: YES
    user_id=850762

    About request #1 (resizing the repair window)...ooops, I
    didn't realize I could drag the bottom or top of the repair
    window. I just noticed the maximize/minimize button in the
    upper right-hand corner was greyed out which usually means a
    window is completely unresizable.

    I have an addition request related to #1 then....could you
    make it so that the repair window is by default MUCH larger
    (top and bottom are stretched larger) OR, make it so the
    repair window will "remember" the last size that I have
    stretched it, otherwise every time I reopen the program I
    have to restretch it again.

    Thanks again.

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks