XYplorer Beta Club

Borut wrote: ↑10 Feb 2020 18:07 And please tell us the meaning/context. Is it like checking on equality vs. checking on similarity, or what?

It's a Status Bar message shown during an image dupe search when Tolerance=0: it means looking very closely because total identity is needed for a dupe.

Yes, it is a second message in status bar, section 3, after message
comparing images <#>/<2:#>... (ESC to stop)
if Tolerance=0 and if you have sufficient number of images to see this message.

As I understand it, during execution action "scrutinizing images", XY select equal hashes from received image hashes and nothing else.
In other words, in the search results for zero-tolerance duplicates, all duplicates have equal hashes.
If this is the case then this action "scrutinizing images" lasts a bit long.

The hashing on Tolerance=0 takes longer, hence the extra message.

Not found:
[messages].Status Log

(Keine ahnung wo es kann sein)

Thanks!

not found:

No user functions declared.
Enter an integer value from 0 thru 9999.
The key '<$k>' isn't found in the list.
Invalid color value.
Deleting cache files failed.
--------------
By the way, I knew that in version 8.109 you deleted 27 lines, but I always thought that you know what you are deleting.

Thanks!

DmFedorov wrote: ↑30 Jun 2020 19:39 By the way, I knew that in version 8.109 you deleted 27 lines, but I always thought that you know what you are deleting.

Next time tell me, please.

If I have two folders: New Folder and New Fólder, then by renaming "New Fólder" with remove diacritics (#139;) I will have such strings, if "Preview all" is not ticked:

The following item could not be renamed:
C:\....\New Fólder
Reason: It would collide with the existing file C:\....\New Folder.
The rename job is now completed. 0 of 1 item have been renamed.

But New Folder is not file, therefor in string "ms.1758=00|Reason: It would collide with the existing file <$p>.\n\n..."
you need have ... existing item..., not ...existing file...

And if I will make this operation with ticked "Preview all", then I will have string "The preview detected <#> <conflict;~s>." not in russian letters.

Ok, changed file to item.

DmFedorov wrote: ↑14 Aug 2020 15:13 And if I will make this operation with ticked "Preview all", then I will have string "The preview detected <#> <conflict;~s>." not in russian letters.

What do you see instead of russian letters?

Never mind, I think I could fix it.

admin wrote: ↑15 Aug 2020 14:48 What do you see instead of russian letters?

I see 1252 encoding: Ïðîñìîòð îáíàðóæèë = Просмотр обнаружил
-----------------------
one more small remark
I want to say, that tip in info pane to "Follow folder links" is not correct:
"Search not only subfolders but also the targets of Shell links to folders."

Search in subfolders I have only if ticked checkbox "include subfolders"

My version: Search targets of Shell links to folders (and subfolders if ticked "Include subfolders").

"Follow folder links" is logically dependent on "include subfolders", so I think the current version is okay. Your version would be misleading.

"Search not only subfolders but also the targets of Shell links to folders."

This hint does not contradict anything if the "Include subfolders" check box is selected.
Without checkbox "include subfolders", there is no search in subfolders of Shell links to folders.
So, It seems to me that Your version may be misleading.

Perhaps this wording will not cause your rejection:
Search in targets of Shell links to folders (including their subfolders, if this specified above).

Thanks, but for me it's okay as it is.

1252 encoding and "file" = "item" is now OK.