Won’t perform comparison with ‘Expected Hash Value’ if entered after hash has been calculated

/Won’t perform comparison with ‘Expected Hash Value’ if entered after hash has been calculated

Won’t perform comparison with ‘Expected Hash Value’ if entered after hash has been calculated

If you select a file to have it’s hash calculated (like after downloading) and enter the ‘Expected Hash Value’ afterwards, it won’t compare the hashes. You have to enter the value first, and then select the file. There should be an ‘AfterUpdate’ event (or equivalent) for the ‘Expected Hash Value’ field to trigger the comparison.

By | 2017-07-14T12:29:53+00:00 June 22nd, 2017|2 Comments

About the Author:

2 Comments

  1. Ted 27/06/2017 at 20:01 - Reply

    I guess I’d never considered that way round before. But I guess it’s a fair point so I’ll look at adding that. Incidentally, v2.8.2 is the current release. Please don’t use the older versions if you can avoid it.

  2. Ted 14/07/2017 at 12:29 - Reply

    An implemented added in v2.8.3 (not released yet) – see commit https://github.com/tedsmith/quickhash/commit/53d2621b9a6fc55a357ef99ffd737ac31a3ee253 . I not sure if it’s the best way of doing it, but it generally works.

Leave a Reply