Firstly I would say: Don't bother.
The filesystem, system caches and disk DD's have access to far more and far better information, from all concurrent activity--not just those processes using your mechanisms--upon which to decide what order to read and write things and when. The very best you could achieve at user-level code is to make things no slower. The likelyhood is that you will not achieve that best.
However, were I to write something along these lines, my starting point would be Jenda's extremely useful Win32::FileOp, which gives you direct access to the OS's own MoveFile and CopyFile functions for the actual file processing parts, along with the OpenDialog(), SaveAsDialog() and BrowseForFolder() functions which are direct access to the systems own GUIs for those functionality. Along with a whole heap of other useful stuff that works with the OS rather than in spite of it.
In reply to Re: Seeking general directions for a Windows specific app
by BrowserUk
in thread Seeking general directions for a Windows specific app
by blazar
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |