Well, you can change them or use them for debugging information - those're the two most common ways that I can think of.
Well, you can change them or use them for debugging information - those're the two most common ways that I can think of.
-Govtcheez
[email protected]
Thnx, but i think i'll need to see a practical case scenario to fully understand its usefulness ^.^.
OK, I'm programming a small micro. There's no easy way to debug it. Fortunately, there is a way to dump the contents of the memory to a .bin file. I can open that with a hex editor and see what values were in memory at the time of the dump. This is very useful in debugging.
-Govtcheez
[email protected]
Sometimes if I need to alter one of the colours in a paletted bit map file, I'll open the .bmp with UltraEdit and manually fix the palette entry. Damn quicker than loading into a graphics editor, extracting the palette, fiddling with it with their "productivity tools" then writing the whole thing back out!
For embedded systems without a good development suite, a hex editor is an essential item.
Wave upon wave of demented avengers march cheerfully out of obscurity unto the dream.
If you have Visual C++, you already have one built in, but it's called the binary editor. Unfortunately, it probably doesn't have all the features of a stand-alone hex editor.
