To reproduce the problem, which renders one of the most useful features of NPP and Hex-Editor unusable, since unreliable, do the following (see Screenshots).
(1) Create any binary file (here: a file containng blocks of 64 bytes). Created one block, open the file in NPP and choose Hex-Editor, works.
(2) Add another block of 64 bytes. Does not work. While the number of bytes displayed in the status line is correct, (128), Hex Editor does still only show the first 64 bytes. Also note that the highlight isn't correct any more, and is arbitrarily moving when you move the Mouse-Cursor over the Hex-Editor Window without clicking something. This annoyance remains until you click anywhere within the highlighted bytes.
(3) To see all the bytes, close the file in NPP and re-open it.
(4) Delete the file. NPP will ask whether to keep the file in memor --> respond yes.
(5) Re-Create the file with one record. NPP will sense the change and ask wether to reload, say yes.
(6_1) Kaboom. The length in the status line is correct (64), but the bytes displayed on screen are completely wrong.
Bytes $00 - $0F are from the new file, and correct.
Bytes $10 - $3F are from the old file
Bytes $40 .. $4F are also from the old file, and exceeding the current file length
Bytes $50 $7F are completely random, have never been contained in the file at all.
Also note that the ASCII column does not match the byte display any more. The annoyance with the sticking highlight is also there.
(6_2) There is also a variant where the old contents of the file will remain in display unchanged, though the file has changed and I responded "y" to the
Long story short: the functionality to reload and display a changed file is completely broken.
Ah forgot the version infos, sorry: latest NPP x32 (8.1) with latest Hex Editor Plugin via Plugins Admin (0.9.9) on Windows 10 x64.
Last edit: ArminLinder 2021-07-03