Column headers and upper case hashes in Log Viewer

1up · 2017-02-07 17:53

Version: Hasher 3.3
Current behavior:

1	X:\1000.bin	1,000	060B1780	ede3d3b685b4e137ba4cb2521329a75e	c577f7a37657053275f3e3ecc06ec22e6b909366	541B3E9DAA09B20BF85FA273E5CBD3E80185AA4EC298E765DB87742B70138A53
2	X:\1024.bin	1,024	EFB5AF2E	0f343b0931126a20f133d67c2b018a3b	60cacbf3d72e1e7834203da608037b1bf83b40e8	5F70BF18A086007016E948B04AED3B82103A36BEA41755B6CDDFAF10ACE3C6EF

Requested change:
Include the column header information when using the "Copy to Clipboard" option from the Log Viewer. This will make it easier for the user to figure out which hash type was used.

#	File		Size	CRC32		MD5					SHA1						SHA256
1	X:\1000.bin	1,000	060B1780	ede3d3b685b4e137ba4cb2521329a75e	c577f7a37657053275f3e3ecc06ec22e6b909366	541B3E9DAA09B20BF85FA273E5CBD3E80185AA4EC298E765DB87742B70138A53
2	X:\1024.bin	1,024	EFB5AF2E	0f343b0931126a20f133d67c2b018a3b	60cacbf3d72e1e7834203da608037b1bf83b40e8	5F70BF18A086007016E948B04AED3B82103A36BEA41755B6CDDFAF10ACE3C6EF

Bug fix: Inconsistent casing for hashes in Log Viewer
Current behavior:
Hashes displayed in the Log Viewer do not conform to the user's Setting for hash casing options (Use upper case hashes - on/off).
The following hashes in the Log Viewer will always display as upper case: CRC32, SHA256, SHA512, RipeMD128, RipeMD160
The following hashes in the Log Viewer will always display as lower case: MD2, MD4, MD5, SHA1, ED2K

Requested fix:
When hashes are added to the Log Viewer, ensure they are added exactly as how they were displayed from the main window at the time they were hashed from the user's Setting for hash casing options (Use upper case hashes - on/off).

Example of requested fix:

#	File		Size	CRC32		MD2					MD4					MD5					SHA1						SHA256									SHA512																	RipeMD128				RipeMD160					ED2K															
1	X:\2048.bin	2,048	f1e8ba9e	318ad28870c004f00c30556606d58bd9	e7b9e6b0e2454e20d7380922c7a0b221	c99a74c555371a433d121f551d6c6398	605db3fdbaff4ba13729371ad0c4fbab3889378e	e5a00aa9991ac8a5ee3109844d84a55583bd20572ad3ffcd42792f3c36b183ad	8785f615b30c07eb4c5f5d72c9b3663521081581ec670631b28be491f5f7ad6c6757b9a2025c68471fa3c9db65305804f6ec6dfd15159b02e91c58ad570e92fb	ff00ea9ec8873116998e39454eaa2339	c0837a8a181405785a0bb89a59fb055132af26a1	e7b9e6b0e2454e20d7380922c7a0b221
	^
	|
	+-- #1: "Use upper case hashes" (in Settings) was unchecked at the time of hashing.

2	X:\2048.bin	2,048	F1E8BA9E	318AD28870C004F00C30556606D58BD9	E7B9E6B0E2454E20D7380922C7A0B221	C99A74C555371A433D121F551D6C6398	605DB3FDBAFF4BA13729371AD0C4FBAB3889378E	E5A00AA9991AC8A5EE3109844D84A55583BD20572AD3FFCD42792F3C36B183AD	8785F615B30C07EB4C5F5D72C9B3663521081581EC670631B28BE491F5F7AD6C6757B9A2025C68471FA3C9DB65305804F6EC6DFD15159B02E91C58AD570E92FB	FF00EA9EC8873116998E39454EAA2339	C0837A8A181405785A0BB89A59FB055132AF26A1	E7B9E6B0E2454E20D7380922C7A0B221
	^
	|
	+-- #2: "Use upper case hashes" (in Settings) was checked at the time of hashing.

Last edited by 1up (2017-02-07 18:23)

den4b · 2017-02-09 18:08

Thank you for a detailed description of the suggested feature and the bug.

Both of those have been addressed in Hasher 3.3.0.1 Beta:

* Respect the setting of upper case hashes option in the Log Viewer.
* Added an option to include header in the Log Viewer export to clipboard.

You will find the newly added option in the Settings.

You can try it from here:
http://www.den4b.com/downloads/hasher

1up · 2017-02-09 22:14

The changes you've made look and work great. I was hoping that the included header information when you copy to clipboard would look better if it was all aligned to match up the rows of information below because as it is now the header information looks squished together (separated by single tabs). But realized that even if you managed to align all that data with the header information, if it looked aligned in one font it might look all botched up in another font. But how you have it works out nicely.

den4b · 2017-02-09 23:56

1up wrote:

I was hoping that the included header information when you copy to clipboard would look better if it was all aligned to match up the rows of information below because as it is now the header information looks squished together (separated by single tabs).

The use of a consistent delimiter makes the file machine readable, hence, easily scriptable. You can also open a tab delimited file in many tabular editors, like MS Excel, and it will be aligned nicely as a table with headers.

As you said, trying to align columns in a plain text editor is a waste of time, because different fonts and editor settings will cause it to misalign.

den4b Forum

#1 2017-02-07 17:53

Column headers and upper case hashes in Log Viewer

#2 2017-02-09 18:08

Re: Column headers and upper case hashes in Log Viewer

#3 2017-02-09 22:14

Re: Column headers and upper case hashes in Log Viewer

#4 2017-02-09 23:56

Re: Column headers and upper case hashes in Log Viewer

Board footer