I've been using NPP with Hex Editor plug-in to view/edit binary files and was very happy with it until I found out that it may display some binary files incorrectly. Hex Editor won't help because the file is already changed when loaded.
I believe the reason is that being it a text editor some binary values are interpreted by NPP as special characters thus causing the problem.
For exampe, try to open a binary file which contains the following 4 bytes: 01 00 82 00 (hex) - create it in another hex editor you trust.
Best of luck,
I had the same idea some time ago. I was going to put it onto
GitHub, so that others could always join as well.
I even already fixed some bugs. The one you mentioned iirc was
due to a missing 'plugins\Config' folder (the code which
creates the folder is a bit messy).
But then I noticed some posts where are mentioned cases when the
plugin shows wrong results. For example:
So I had a closer look at it for some time and realized that
you can actually never trust this plugin due to the whole
technical approach. It 'only' shows the hex values of the content
given by scintilla, which often differs to the real content (on disk).
That's why I lost my motivation. It really requires a total rewrite
of the way it gets its content: It has to read it from the device itself
or rather find a way to pipe it past scintilla's encoding parser etc..
Good luck and I hope somebody can prove me wrong!
lol.. pasted into wrong thread ^^