Locate32 does not show (all) information about files that are not present (what it calls “deleted files”).
For example, if you index a removeable drive and then remove it, or index a drive on another system, then Locate32 will display the names of the files and folders that are not currently present, and will show their Types as “Deleted File/Folder”, but it will not show their dates or sizes.
This is an unnecessary limitation. Locate32 has already gathered a lot of metedata about the files and folders, and even though the files or folders are not actually accessible at the moment (regardless of whether it’s because they are offline or deleted), Locate32 should still show as much metadata as possible.
In fact, Locate32 does actually show the other metadata while it is populating the list, but then it removes them once it has finished and flags them as unavailable.
It is already flagging them as offline/deleted by showing “Deleted” as the file-type, so there is no reason not to show the dates, size, and other metadata that has already been collected.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I ran in to a similar problem in that I couldn't search a database for an external HDD when it wasn't connected. And I already had the box ticked to "Disable updating (file information from database)". What I had to do was also un-tick "Do not show deleted/renamed/moved files". But obviously it shouldn't work that way, so that appears to be a bug.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If kind of worked as it was supposed to work. "deleted/renamed/moved files" means files that cannot be accessed at the current moment in the location stored in the database. Locate32 does not option to separate a case that files are somewhere in non-connected remote device or are deleted.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yeah, it works. It's just that the name of the setting is misleading because files that have been renamed, etc, are changed - not offline. So that setting implies that the app is only tracking the status of changed files. But it actually does more than that, and the Help file doesn't explain it.
Anyways, thanks for the fast response.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Locate32 does not show (all) information about files that are not present (what it calls “deleted files”).
For example, if you index a removeable drive and then remove it, or index a drive on another system, then Locate32 will display the names of the files and folders that are not currently present, and will show their Types as “Deleted File/Folder”, but it will not show their dates or sizes.
This is an unnecessary limitation. Locate32 has already gathered a lot of metedata about the files and folders, and even though the files or folders are not actually accessible at the moment (regardless of whether it’s because they are offline or deleted), Locate32 should still show as much metadata as possible.
In fact, Locate32 does actually show the other metadata while it is populating the list, but then it removes them once it has finished and flags them as unavailable.
It is already flagging them as offline/deleted by showing “Deleted” as the file-type, so there is no reason not to show the dates, size, and other metadata that has already been collected.
You could try "Disable updating (file information from database)" optin in Advanced settings.
I ran in to a similar problem in that I couldn't search a database for an external HDD when it wasn't connected. And I already had the box ticked to "Disable updating (file information from database)". What I had to do was also un-tick "Do not show deleted/renamed/moved files". But obviously it shouldn't work that way, so that appears to be a bug.
Hi,
If kind of worked as it was supposed to work. "deleted/renamed/moved files" means files that cannot be accessed at the current moment in the location stored in the database. Locate32 does not option to separate a case that files are somewhere in non-connected remote device or are deleted.
Yeah, it works. It's just that the name of the setting is misleading because files that have been renamed, etc, are changed - not offline. So that setting implies that the app is only tracking the status of changed files. But it actually does more than that, and the Help file doesn't explain it.
Anyways, thanks for the fast response.
Well yes, but to be more precise Locate32 does less than that as it only checks if the file is still accessible in the location.
But anyway, the development of Locate32 is discontinued (unless there will be someone coming to take the control)