In the past I made mistakes in forms and didn't pay attention to the location of a preference in the preference-tree. Putting my mistakes aside in this Topic.
Does the "Get Sizes" button/command follow Junctions/Symbolic Links? It seems it does, compared to GoodSync when syncing the folder with copy the mentioned "As Is" without following the content. Could the Size in Dopus reflect the actual size? Like the Folder Windows Properties General Tab in terms of the actual value, except generated through Dopus faster?
Yes, it follows junctions and links. It will tell you the size needed to copy the selection to another folder.
Outside of scripting (e.g. a script column), there isn't a way to change the behaviour at present.
There is the option Preferences / Folders / Folder Behaviour / Skip junctions and softlinks but I believe it only applies to automatic calculation (the option it's a child of), and may only skip things at the top-level.
Is it difficult to get a 2nd button that by default behaves according to an associated preference? The automatic one isn't practical when moving around too much to many drives with huge top-level folders.
The preference of the 2nd button should then be able to be specified that any encountered Special Link can be ignored, to see the actual size on the Drive, not a normal Windows Explorer or Dopus move from Drive to Drive, but rather moving within the same drive (doesn't copy content of the Special Links, but moves them) or moves/copies with Syncing Programs including freefilesync.org/ with which Special Links can be also ignored OR preferebly copied as is. Such programs are currently the only way to know the actual size of a folder, to know where I can look to get rid of unnecessary stuff.
I want Dopus to help me do that more easily throughout my life. Any help in this regard? Any code I can currently apply for the scripting column to achieve that on the get go for the time being? Worst case I've to figure things out, but that will take me a while, I've complications all over. And with my 'head', my mistakes are scattered on each corner in my life.
If you're moving folders on the same drive then the reported size isn't important, since moving the folder won't make it take up any more or less space than it already does.
Is it worth it to be a feature request? Any plans for it? Should it remain through scripting alone?
It might not seem like a big deal, if I get the scripting to work, but I had to adapt to the Dopus calculated sizes method, instead of getting the answer I was looking for.
Thank you in advance for tentative addition to the todo-back-logs if you agree.
It is if I'm sorting a big drive, I could then easily know, what folders to sort out later, and what now. That's also my use-case, it doesn't have to be someone else. SW technicality, it's not difficult to set the default behaviour for the manual get sizes button just like the automated calculation, which slows down the otherwise at least good experience and uses resources when not needed, so turned-off by default in my case.
It is if I'm sorting a big drive, I could then easily know, what folders to sort out later, and what now. That's also my use-case, it doesn't have to be someone else. SW technicality, it's not difficult to set the default behaviour for the manual get sizes button just like the automated calculation, which slows down the otherwise at least good experience and uses resources when not needed, so turned-off by default in my case.[/quote]
It's about to know, where to look, to possibly know, what I might want to delete. That's the core of my use-case. Also I could instead THEN choose to move a portion to another drive, in a heartbeat, instead of thinking of the statements for the use-case.
It's also to group bunches used more often, and others not so often, to sync separately, one job used more often, but less data, the other less frequently, but takes up a lot more time. If you don't use Special Links as heavily as I or others do, the status quo won't bother you. I've Special Link sprinkled EVERYWHERE for one purpose or the other, to reuse files, centralize and efficiency. It's really resorted me using Syncing apps/programs to find out what's actually what size.
Also beware of infinite recursive Special Links, there is no end size. It happens sometimes for special use-cases. Of course I've long ago learned to avoid relying on Dopus sizes where Special Links is involved.
The less problematic, but readily reproducible, is the Get Size of the C:\Users Directory, that simply returns an untrue value (total of in Windows and in Users folders can not exceed the currently used space on the partition). It returns a value that ITSELF (Dopus) will need while copying to point B, meaning making duplicates if a user profile is moved to another partition (or any relevant situation similar to that use-case). I use GoodSync (above Open Source alternative works well, GoodSync is for me the way to go when syncing heavily lots of things to at least a few drives) to copy the Junctions "As Is". Downside is that "Restore Points" won't work and will corrupt the registry hive of a user-profile, when a user profile is Symbolically Linked back to C:\Users, but I don't use "Restore Points" anyway, and want to be able to restore to a previous Windows-state/C-partition-image (past anti-BSOD-hell habit) without losing my app user profile settings. This is just to give a personal background for the relevancy of the sizes in C:\Users, and with that any relatively frequent and intermingled occurrence of Special Links.
I'm not sure I'm making any sense, is there any interest in providing the option also for the manual button instead of only to the automatic calculation?
I wanted to share my appreciation for Dopus and the support. One day it might become perfect. Although it's pretty close, despite some of my past assumptions.
