As I stated, I might be talking about a different problem. I'm sleepy and need to go to bed to get up for work (it's past midnight where I'm at), so I don't feel like taking screenshots, cropping them, hosting them, and then posting them, so bear with me.
Attach to a process and then bring up the Hex Editor.
Clicking on a byte will update the helper window to show you all the possible data values (byte[8-bit], short[16-bit], long[32-bit], float[32-bit], etc.) at that location. To set the byte selection to the next byte, one has to click on it with the mouse. Using the arrow keys just moves the editing cursor and not the selection cursor, therefore, the conversion window remains unaffected.
I suppose this is probably by
design, so I guess I'm really saying there should an option to change this behavior. In this type of application where we are blindly perusing the raw data to find some known data (or more so, a structure we defined in your fabulous template designer), it is general practice to scroll the data
quickly with the arrows/keyboard. Having to manually click each individual byte in a sea of thousands is inefficient.
Every debugger I have ever worked with (and there have been many) work this way, so I guess that's why I find your method unintuitive and cumbersome, particularly given the purpose we are using your tool for in the first place. *shrug*
So in conclusion, I'll concede it's not a bug.
But I still would love for you to add a way to scroll the memory with just the keyboard and not have to rely on mouse clicks. That's all I'm saying.