Marking the Memory Area with Color Explicitly

[zxcev]

Is your feature request related to a problem? Please describe.

Hello,

I am very grateful for your efforts, which have enabled the use of memory view in VSCode. While studying C language using CLion, I gained many insights through its memory view feature. I am delighted to have this functionality now in my preferred editor, VSCode.

However, there's one feature I feel is missing, and I apologize if I've overlooked it since I haven't used it extensively yet.

Currently, in memview's memory view, when tracking a specific variable in memory, it highlights the changed bytes in green when the values in that memory space change.

However, when tracking the memory space itself where &a is located, it doesn't seem to color-mark the position or size of &a.

---

Describe the solution you'd like

In CLion, for instance, the memory space occupied by &a is colored like below.

it makes easier to use the memory view. It would be greatly beneficial, especially for beginners like me, if such a feature were added to memview as well. In CLion, the tracked memory area is highlighted in light green, and changed bytes are marked in orange like below.

---

Even without this feature, memview is very helpful to me, and I hope it continues to be widely used and developed further. Thank you for creating such an �amazing extension.🙇‍♂️

[haneefdm]

Thank you for the kind words.

However, when tracking the memory space itself where &a is located, it doesn't seem to color-mark the position or size of &a.

The method for highlighting is always the same. Can you make sure your address ranges are correct. I see totally different ranges between all the screenshots so, it is hard for me to tell what is going on.

The way highlighting works is that every time the program pauses for whatever reason, we do a delta. So, the history is only one level deep. Let's say you do two single steps kinda fast, you may not see the changed bytes at all. Especially if you single step at an assembly level. Please let me know the steps to reproduce the issue.

I can see that our decoded bytes look a little bit messy. But instead of a dot, I still find it more useful to know what character it represents. I am a C/C++ desktop and embedded programmer myself.

Finally, the colors chosen are actually from your VSCode theme. I didn't pick or hardcode them.