Hex editor improperly displays the values of addresses when a cheat size smaller than the data size is applied to one of the addresses

[NarryG]

If you apply a cheat that's smaller than the displayed data size of the memory domain, the hex editor will mis-report the values in memory.

If you swap to 1-byte mode, you'll see the actual values.

[alyosha-tas]

This one is trickier to solve then the other one.

For reference, the problem lies in GenerateMemoryViewString, line 512 of HexEditor.cs

The code pulls in the displayed number of bytes even if a cheat only effects one byte. I'm not sure when I'll sort this out but that's the place to start if anyone is interested.