Bug in the copy progress bar of WB 3.9

[AmigaMance]

I wonder if someone else has noticed this bug.
 I have install the latest versions of icon and workbench library from the unofficial update, but iirc, it happens with the BB #2 update too. I don't use AsyncWB because it doesn't behave very well:
 When i try to copy large files across partitions, the copy window appears and the progress bar begins to grow, as it normally should. Then, all of the sudden, the progress bar disappears (not the window) and remains this way for the rest of the copy process. The file is copied ok.

[AmigaMance]

[/quote]I wonder if someone else has noticed this bug.[/quote]
 No? Ok. :-)

[Thomas]

It probably only happens with very big files. I suppose it happens when the file size multiplied by the width of the status window results in a number which is bigger than 2GB or bigger than 4GB. Then an overflow occurs and the result is either negative or very small which causes the progress bar to disappear.

I assume there are not many people who use Workbench to copy files at all and if they do, they probably don't disable AsyncWB.

Bye,
Thomas

[LoadWB]

Thomas wrote:

I assume there are not many people who use Workbench to copy files at all and if they do, they probably don't disable AsyncWB.

Largest file I copy with Workbench has been around 800MB with AsyncWB active.  I certainly haven't noticed this problem.  Generally, though, I'm using DOpus, CLI copy, or smbclient to copy files.

[AmigaMance]

 Yes, it looks like some sort of overflow, but it doesn't happen with very big files only. I haven't found the minimum file size where the bug occurs, but it happens with a 100MB file, for instance.
 As for AsyncWB, it causes real problems unlike this one. For example, select more than one file, then try to duplicate them (icons -> copy) and watch what happens. It's better to be left alone.

[wurzel]

Thomas wrote:
....
I assume there are not many people who use Workbench to copy files at all and if they do, they probably don't disable AsyncWB.

Bye,
Thomas

I only use WB to copy files when the filename is too long for DOPUS4. I never really took to DOpus5.

Only today, I was copying over mp3's with very long names, and had to use WB. Each one was an average of 4mb and I copied them in blocks of 5. I didn't suffer the problem described by the oirignal poster, but I have AsyncWB enabled as well.

[stefcep2]

AmigaMance wrote:
 Yes, it looks like some sort of overflow, but it doesn't happen with very big files only. I haven't found the minimum file size where the bug occurs, but it happens with a 100MB file, for instance.
 As for AsyncWB, it causes real problems unlike this one. For example, select more than one file, then try to duplicate them (icons -> copy) and watch what happens. It's better to be left alone.

A single file 100mb in size is positively HUGE for an Amiga.  The file size is probably what's causing it.  Remember, A1200 came with a 40 mb drive as standard and that was enough to hold the OS, Apps, games, images etc