Ticket #173 (closed defect: fixed)

Opened 6 years ago

Last modified 6 years ago

Odd Progress Bar Result.

Reported by: Overwriter Owned by: Joel
Priority: major Milestone: Eraser 6.0
Component: Core Version: 6.0.4.875
Keywords: Cc:
Processor Architecture: Blocked By:
Blocking: Operating System:

Description

XP Pro SP3 .Net 3.5 Beta 4

Hi

When erasing a floppy I get this.

My display stays like the top image for some time without changing then suddenly jumps to the second image.

Also if you notice my “Running” progress bar isn’t full although the task is complete.

Thanks.

Blocking

IdSummaryMilestone
#173Odd Progress Bar Result.Eraser 6.0

Blocked by

IdSummaryMilestone
#173Odd Progress Bar Result.Eraser 6.0

Attachments

Progress Display.jpg (164.2 KB) - added by Overwriter 6 years ago.

Change History

Changed 6 years ago by Overwriter

comment:1 Changed 6 years ago by Joel

  • Status changed from new to accepted
  • Owner set to Joel
  • Milestone set to Eraser 6.0

Yes that's what I meant by my untested floppy disk code. THe progress dialog waits for a bit of progress to be made and for the program to "Report back" to the dialog for progress information instead of asking the executor for progress. In floppy disks this takes quite a while, but for other media it's quite instantaneous.

I'll have a think.

comment:2 Changed 6 years ago by Overwriter

Hi Joel.

I think I understand what is happening here.

I take it in order to make the progress bar more accurate in other situations you take a long snapshot as it were in order to work it out better.

I take it by the time this snapshot has been taken and assessed by V6 the floppy has been overwritten !!

If this guess is right is there a way that Eraser could tell / sense that it is a floppy disk it is overwriting and adjust the snapshot time accordingly ?

Perhaps this is the case for other media ? Flash, cards and ZIP drives etc ?

Thanks Joel I understand this is a trivial matter but I understand the “teams” desire to seek perfection !!!

comment:3 Changed 6 years ago by Joel

Yeah, something like that. Progress updates are available only after a bit of the drive has been overwritten. However, in floppies this little bit takes forever so the update is never done. I don't think it's possible to adjust the time taken because it is dependent on how fast the drive can write a block of data Eraser presents it.

comment:4 Changed 6 years ago by Joel

  • Status changed from accepted to closed
  • Resolution set to wontfix

I can't think of any way to solve this (even after so many months). This is currently the optimal solution I can think of so I'll close this. If anyone else finds a better solution reopen this ticket and describe your procedure please.

comment:5 Changed 6 years ago by Joel

  • Status changed from closed to reopened
  • Resolution wontfix deleted

comment:6 Changed 6 years ago by Joel

  • Status changed from reopened to accepted

I think one solution ill be to change the labels on the progress dialogs to tell the user that the information is being gathered while the operation continues so the user will know that he has to wait for the next 'snapshot'

comment:7 Changed 6 years ago by Joel

  • Status changed from accepted to closed
  • Resolution set to fixed

Fixed in r896

Note: See TracTickets for help on using tickets.