From: Christophe B. <to...@to...> - 2004-04-02 17:14:58
|
Le mer 31/03/2004 =E0 19:45, Jonatan Liljedahl a =E9crit : > Couldn't you just read the destination file(s) size continiously (0.5 > sec interval or something) and calculate what procent to feed the > progressbar widget? Yes, that's a solution, a dirty one IMHO, but a solution (before knowing vcp I was using a 5-lines script with "du" and "cp"). But the main problem is to read the source file size. That's ok for one file, but if you have a whole arbo (i.e. /usr/src/linux), it's quite... long, and resourceconsuming (IIRC, explorer on MS Windows does it this way... beuark). A simple solution could be to start the source size counting in a thread, the dest size in another thread, while beginning the copy in a third. So we would show "40 Mb / ??? copied", like an http download without knowing the content-lenght. As soon as the source size is known, only the second and the third thread exist, while showing "60 Mb / 120 Mb copied (50 % - 45s left)". Why, a dirty solution ? - a fork to call "du" for the source file(s) - a fork every "update" to call "du" for the dest file(s) - a fork for the "cp" command I prefer rox the way it is now than a resource consuming like this... That's my opinion, of course, it may be a solution. --=20 Tof PS: Sorry Jonatan I sent you this mail to your address by accident |