I can just hear the response now. "More junction stuff. Great."
I've been making a fair bit of use of junctions since adding a lot more space to this machine. I've always hated having a zillion drive letters and having to remember where I put what. Being able to graft new space onto an existing directory structure is great.
Noticed a bit of a snag tonight when moving things around. When trying to move some files through a junction to a different volume, DOpus comes up with some kind of permissions error. I understand what's happening -- it's trying to do a rename/move across device boundaries and Windows is complaining. This seems a rather inelegant way of dealing with the problem. I would expect nothing better of Windows, but of DOpus, ...
I think it's reasonable to assume the user expects the files to be "moved" in this situation. It's what would happen if the target folder was on the same volume. To the less-informed user, the target appears to be on the same volume. The drive letter is the same. Part of the point of junctions is to not have to worry about the physical structure. It's supposed to look like one big folder structure and it seems reasonable to expect the tools to act as though it were.
Having normal file operations suddenly fail with rather cryptic, and, frankly, wrong, error messages isn't very helpful. So I would think the ideal thing would be for DOpus to attempt a normal cross-device move (i.e. copy/delete) of the objects in question. It does this when explicitly moving files across volume boundaries. It seems reasonable to do so when the cross-volume operation is through a junction to a folder that looks to the user like any other folder on that drive. At the very least the user should be presented with a pop-up explaining the situation and asking whether the objects should be moved, copied, or the operation aborted.
