Hey again Kirk-
totally understood about the coasters... but there are also many times when we'd love to be able to be working in separate contact sheets... PM4 is super speedy and efficient for our tasks with any given sets of images, but unfortunately sometimes it's not just about running one set of pictures through a workflow...
often times we're faced with situations where it's burning a disk of project A while editing down pictures from project B while running a big batch save-as of another series of images combined from contact sheets of projects C, D and E... and then a client calls and they *urgently* need a file from project F emailed to them.
so if things like disk burning, "save-as", html export, etc etc could operate as separate processes without locking up the whole app, it would be very helpful.
Again, I think this could be possible if you developed a mechanism whereby PM4 kept a checklist of which files it had queued up for such activities as burning and what not, and presented you with a warning along the lines of "this file is in use by this process- are you *sure* you want to modify it now? this may result in a failure of your burn/export/saveas/ftp/whatever task" -
Having such a mechanism would prevent people from stupidly creating coasters, and yet allow users more flexibility in multitasking within photomechanic. The question is whether this is feasible, and worth the hastle, and useful to enough other people besides the two of us mentioning it here..
thanks!
-jj