mh-nexus.de

https://github.com/maelh/hxd-plugin-framework

Let me know how it goes.

https://github.com/maelh/hxd-plugin-framework

Let me know how it goes.

I have the plugin framework almost ready, and will publish it on GitHub with instructions soon.

Are you ready to test it and let me know of any issues?

Since a couple people have voiced interest in extending the data inspector, I will add a plugin interface.

Since a couple people have voiced interest in extending the data inspector, I will add a plugin interface.

As this is offtopic to HxD, and not really helping its development I moved this.

Will not be easy (since I need to make a special decoder for float16 to string values and back -- this doesn't come by default in most languages). But should be well documented and useful. P.S.: What would you need it for? I mostly know of float16 being used in deep learning, but I don't see why you...

Let me know if you are interested in this plugin approach, as mentioned in my last mail.

From previous email exchange: It could be added to the data inspector. The basic unsigned format seems reasonably simple, the more compact ones less. I found this article https://en.wikipedia.org/wiki/Variable-length_quantity which also describes the Git encoding. However it is slightly confusing an...

Note for future implementation: Another thing that will have to change, is that currently the passes are done only in memory It is comforting that one pass is probably enough. But with high degree of chaotic randomness. The "wipe securely" function under tools/extras will use several passes (if you...

Note for future implementation: Another thing that will have to change, is that currently the passes are done only in memory (except if you chose wipe file). This allows for undo, but defeats the purpose of multi-pass wiping a portion of the file/disk, for example. So a direct mode would be necessar...

Instead it should display as C0, the same way as UInt8. This is due to converting it to a signed Int8 that is then passed on to a (U)Int32 or an (U)Int64, at which point a sign extension happens, which show as leading F's. Also look how others handle this, as usually hexadecimals are always positive...

When changing the casing for hexadecimal offsets or numbers in the options dialog, the TXmHexEdit ist updated, but not the data inspector, and not the status bar. Should watch/subscribe to an update event (that watches this specific option change), and then refresh the display of statusbar/data insp...

Thanks for the link of this nice compact code.
From what I can tell it is only for floating points numbers, though. I am not sure how well the guarantees transfer to integers.

It came from a resize while designing that went unnoticed, since the settings where different in the local INI file. Thanks for reporting.

Fixed in the development version.