File copy with progress bar

Looks like homework. What has your instructor told you recently?

I'm guessing you've been learning about opening and closing files, and also reading/writing data. Do that.

Out in the real world you'd use asynchronous OS calls, but that is probably far too advanced for now.

Think about the problem and break it down into steps. Write down the steps here and then tell us what part are you stuck on?

looks also like they told you something about threads ;)

looks also like they told you something about threads ;)

what does threads have to do with this?

Threads only complicate things here, as the OP has yet to figure out how to do it sequentially.

Even if you know how to do that, you probably don't really need threads. Disk-speed is an order of magnitude slower than the CPU, and disk-cache read-ahead will make sure for ample supply of next data blocks. Maybe with an SSD that changes, but then a progress-bar makes no sense any more either :p

There are OS-specific techniques that can potentially do it in the background without the data ever touching the CPU or other higher-performance patterns.

Based on the wording, it looks like something that could be accomplished in about 10 lines of code if you know what you are doing. Open the files, find the length, read and write, update status. Rinse and repeat until done. Close the files.

I'm pretty sure I had the same assignment back in my college days.

looks also like they told you something about threads ;)

what does threads have to do with this?

Yeah I'm sure they said to avoid them at all costs :D

.

That's nice. But your post is not very useful by itself. Don't be lazy, and respect the time of the people who are here voluntarily helping you.

Did you test it?

Does it work?

Does it NOT work?

Can you break it?

How does it break?

Can you speculate as to why it might be broken?


Also, if this is homework, please keep in mind that site policy is that we do not help with homework. Ask your teacher/professor/mentor.