Search hex string is a good option when we need to find a binary sequence in a file. However, it does not always inform about unsuccessful result. This happens when the text sample, input in the search box, cannot be properly converted to hex values, often by mistake or mistype.
For example, let open for view the file HISTORY.TXT from TC, set the hex string search mode and input the text: 0d0a32
Lister immediately finds the first line starting from symbol "2": 0d0a is CRLF (next line), 32 is hex code of "2".
Modify the search text to odoa32 (replace zero with small letter "o" in 2 places).
Lister informs that text is not found, it looks like correct result, but the sample text is not a hex sequence.
Modify the search to od0a32 (replace only first zero with "o"). Lister finds nothing and shows no error. This is definitely wrong.
Lister should check that search text can be converted to hex characters and inform about error, which will allow a user to easily fix the mistake. In particular, both odoa32 and od0a32 should result in the same error message.
Lister: "Search hex string" should inform of incorrect text
Moderators: Hacker, petermad, Stefan2, white
Lister: "Search hex string" should inform of incorrect text
Desktop: Windows 11 Pro 23H2, TC 11.50. Mobile: Pixel 5a, Android 14, TC 3.60b4
Re: Lister: "Search hex string" should inform of incorrect text
Sorry thats a "you-problem". You should be able to insert a correct code and not make it TCs job if you are able to do soSlavic wrote: 2024-02-06, 17:30 UTC Lister informs that text is not found, it looks like correct result, but the sample text is not a hex sequence.

Otherwise you want next TC to check if a user enters reg-ex correcty, etc
This is correct and should be fixed.Slavic wrote: 2024-02-06, 17:30 UTCModify the search to od0a32 (replace only first zero with "o"). Lister finds nothing and shows no error. This is definitely wrong.
I doesnt give an error message but still makes an error PING-sound.
Hoecker sie sind raus!
Re: Lister: "Search hex string" should inform of incorrect text
Incorrect. Basic input checking is a common and preferable practice.
This is covered; there would be a messagebox in case of a bad regular expression.Sir_SiLvA wrote: 2024-02-06, 18:41 UTC Otherwise you want next TC to check if a user enters reg-ex correcty, etc
Sound-only diagnostic is not that great; visual indication is more natural - because it is GUI.Slavic wrote: 2024-02-06, 17:30 UTC I doesnt give an error message but still makes an error PING-sound.