Note that when original referenced file is moved/deleted (incl. Upon deletion from Paper Folder (or equivalent like move), the reference is removed from the text file, but nothing is done to the original (referenced) file. From that point, the filename shows up as present in the Paper Folder, but any file operations (drag-copy out, etc.) are essentially invoked against the referenced original file. I might take a look at writing one if I have time, first need to see how well the SDK describes the requirements for virtual folder plugins (as that seems where "storage vs reference" issues are most likely to arise during implementation).īTW, because it isn't immediately obvious from the Paper Folders description: When a file is added to a Paper Folder, the original location (path/name) is what is stored in the text file. AFAICT, the missing piece for DO having equivalent functionality is the "text file" virtual folder plugin element. As I understand it, "Drop Stacks" just refers to the precise way drag-and-drop works when the folder target is a "Paper Folder" - as I understand it, previously Xyplorer couldn't drag/drop to Paper Folders, unlike other types of virtual folders. Once there's support for a virtual folder type that's stored as a text file, then depending on how add/remove file/folder are implemented, potentially DO's "folder reference buttons" would just work akin to Xyplorer's "Drop Stacks". You can configure buttons in Opus to copy files to a specific folder (including a file collection), and files dropped on it will go to that location automatically - is that what "Drop Stacks" are?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |