psguru wrote: Sun Oct 13, 2019 4:00 pm
Showing empty directories in recursive comparison is optional, as you probably know, and it's off by default. The message you suggest would only make sense in non-recursive comparison (there are no non-empty folders in recursive comparison), but then again, EDP does not spend time to calculate empty/non-empty in that mode, and what would be the benefit of knowing that some folders are empty in non-recursive comparison?
Showing empty... is on, here.
> "there are no non-empty folders in recursive comparison"
- by which you mean that your display can only show recursive contents of some folder if it actually has contents, which does make sense.
But I think in some ways you're "too close" to the nuances of comparing things. Maybe it's naive, but generally if I'm comparing two lists of anything, I want to see all the items in both lists and their corresponding statuses. If I choose to exclude things from the lists I can choose to filter what's considered or let all the comparisons occur and then filter the display ... but then, I know I did that.
If folders that I know exist don't show up in a list, then I wonder if other things which should have been there are for some reason not shown - and that removes my confidence in the display. EDP is very clever, but in all that cleverness there's already considerable scope for a user confusing themselves by forgetting which options are set which way. For that reason I tend most of the time to have "show everything" and "compare stuff in great detail" set, because I'm not that bothered if a compare takes a bit longer, but I /really/ want to know if things that I expect to be the same are not. Also, time issues are a lot less relevant for me now that all my machine's disks are SSDs. A comparison tool is after all often used to make sure that all the files/folders you look at are in the right state, and that certainly includes being present.
It seems to me that it would be simple to have every folder, empty or not, show up in the results list. You already know whether or not there's any point in recursing into each one. Bear in mind that if I use the very simple "dir /s" command it will show me every folder, empty or not.
> what would be the benefit of knowing that some folders are empty in non-recursive comparison?
Seriously? Your product already DOES tell me that. It lets me see if lefthand and righthand pairs of matchining folders have the same empty/not empty state.
I think you're forgetting that when someone compares a set of folders and files they do so after they've done something or other to one set of them (or maybe both sets). Suppose I'd just run some tool that was meant to empty out some directories but not others. I might be using EDP to check that the expected differences are present but no unexpected ones are there. I definotely want to see that empty directories are there, and that they are where I expect them to be.