<caution - rant!>
i'm trying to retrieve some old work of a pretty ancient archive CD and naturally the finder is playing silly buggers. i drag the folder i want - full of several other folders, subfolders and files etc. - from the CD to my hard drive and watch that progress bar crawl.
then, what with it being an old CD come the inevitable read/write errors [anyone else remember how when first invented CDs were touted as being 'virtually indestructable' - ha! ha!]. so the finder pops up a dialogue telling me that 'xxxxxx.xxx' could not be copied because of a read error. i OK the dialogue and the copy operation bombs out.
for feck's sake! - now i have to go through all these multiple nested folders trying to find the file that stopped the copy operation and then try and resume copying by selecting everything else apart from that item [which is fun with nested folders!] and dragging them to the destination disc in all the appropriate places - until the next read error comes along!
why does the finder do this? it's irritated the hell out of me from the first day i ever used a mac and it still does. if i'm copying a load of things from one location to another and you can't read one of them, then copy the rest of the f**kin things you can read! then afterwards you can present me with a report window which tells me which ones you couldn't read. why on earth assume that because you couldn't read one item, i want to give up trying to copy everything else too - you dumb POS!
now. i realise that implementing sexy drop shadows and 'good enough to lick' buttons is much more important than actually making basic file operations behave more helpfully, but i wonder if there's any chance this could be attended to within the next 20 glorious years?
</ rant!>
?
Top
