I understand where you're coming from in that implementing features for *general* purpose file management opens up a pandoras box of features and bugs to fix to implement it right. That said, I think for the *specific* purpose of processing RAW images, folder movement is a must. 50% of my job is image file organization/processing, and I've never had a workflow that doesn't involve creating folders and sorting images into them.
I don't think you'd need to account for symbolic links and special files...only moving a folder full of images and sidecard files produced by the camera and RAW processing software. If there were a warning that FastRawViewer cannot handle symbolic links, etc, I feel that would be fine? As far as I know, even Finder on Mac will break symbolic links if you move a folder...so it's not common to account for that.
If you're committed to not implementing it, that's your choice of course. I'm just letting you know that the lack of this feature is the only thing holding me back from recommending this app to others in my industry, and probably using it myself going forward. I process 1000's of images a week, and the speed of your app to read and QC the RAW images is unparalleled, but the speed gains are lost if I have to open Finder every time I want to move a folder.
Thanks for the response, and wish you the best with future development.
I understand where you're
I understand where you're coming from in that implementing features for *general* purpose file management opens up a pandoras box of features and bugs to fix to implement it right. That said, I think for the *specific* purpose of processing RAW images, folder movement is a must. 50% of my job is image file organization/processing, and I've never had a workflow that doesn't involve creating folders and sorting images into them.
I don't think you'd need to account for symbolic links and special files...only moving a folder full of images and sidecard files produced by the camera and RAW processing software. If there were a warning that FastRawViewer cannot handle symbolic links, etc, I feel that would be fine? As far as I know, even Finder on Mac will break symbolic links if you move a folder...so it's not common to account for that.
If you're committed to not implementing it, that's your choice of course. I'm just letting you know that the lack of this feature is the only thing holding me back from recommending this app to others in my industry, and probably using it myself going forward. I process 1000's of images a week, and the speed of your app to read and QC the RAW images is unparalleled, but the speed gains are lost if I have to open Finder every time I want to move a folder.
Thanks for the response, and wish you the best with future development.