#Hard errors?
Actually, we do care about Workbench. Copy is single threaded because
there's no better way for a new user to thrash (and, under V1.1) trash a
file system then allowing copies and deletes to happen at the same time.
Remember that there really is no firm indication of directory structure
from Workbench. So if a Workbench user launches a recursive copy, then a
delete of one of the files in the hash chain…
Workbench is a single application. Its not always desirable to put
multitasking within an application. Look at the early Textcraft, with its
seperate tasks to handle input, display, and scrolling. Multitasking should
be used judiciously within a program.
Now that I've said that; there are places in Workbench where use of
seperate tasks would do wonders. A task dedicated to refreshing the
windows, for instance.
Workbench is coming out of the ROMs for V1.4, to make room. We haven't
made the 512K decision yet (the one that forces A1000 owners to use roms
as well) so something had to give, and it turned out to be Workbench. Once
out of the ROMs, Workbench will be a bit freer to stretch a little, so to
speak, and can gain functions other than just bug fixes.
A handy tip: when using Workbench to duplicate drawers (or whatever), move
the thing being duplicated onto the backdrop window while duplicating.
This will speed the operation greatly, and cut way down on memory usage.
Ben: pretend I didn't say that stuff up there about 1.4, and just mentioned
the handy tip (grin)