{"id":41754,"date":"2024-01-11T14:22:36","date_gmt":"2024-01-11T19:22:36","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=41754"},"modified":"2024-01-11T14:22:36","modified_gmt":"2024-01-11T19:22:36","slug":"displaying-progress-is-hard","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2024\/01\/11\/displaying-progress-is-hard\/","title":{"rendered":"Displaying Progress Is Hard"},"content":{"rendered":"

Howard Oakley<\/a>:<\/p>\n

\n

When I copied some files from iCloud Drive, instead of seeing a progress indicator reporting that they were being downloaded from iCloud, the dialog claimed that it was “preparing to move” the document in question. These preparations took some considerable time, during which the Finder’s status bar revealed what was actually taking the time: it was “downloading 1 item”, and reported its progress in doing so. For much of that time, the progress bar in the dialog showed that its ‘preparations’ were actually complete.<\/p>\n

[…]<\/p>\n

What happens when the sparse file can preserve the special format during copying, is that the determinate progress bar assumes the worst, and the full size of the file is used to calculate progress. When the amount of data transferred reaches the sparse file size on the destination, long before the bar has even got to 50%, the copy suddenly completes, apparently after only a small part of the task has been completed, leaving the user as surprised as the Finder must have been.<\/p>\n

Unfortunately, there appears to be no way to discover in advance how much data will need to be transferred.<\/p>\n<\/blockquote>\n\n

Previously:<\/p>\n