Improvements to memory view in debugger [Imported Thread]
I would be nice with a better indication of which memory cells are being switched of / not present. Today the debugger shows random data in such an area.
When you move/slide you view across the boundary between "good"/present/enabled memory cells and into an empty / disabled area. Then the whole buffer gets garbled, not just the cells in empty area.
Couldn't the empty/switched of cells and ONLY those be represented by something else a say "?" and the good ones by its actual value? Anything else than a garbled buffer would be really nice.
The possibility of sliding the window by using the arrows keys and pg up / pg down instead of only by muse clicks could help prevent soar programmers fingers.
If I'm working a range of memory that's bigger than what can be shown on the screen and inspecting a cell which I have to scroll down to in order to inspect, then it's annoying that my view gets reset to the start of the buffer every time I press F10 to step the program forward.
That's annoying especially if I have to click and scroll a lot to get back to that cell again
Cheers
Spang
Idea Originally Posted by: Spang Kuk 20/04/2013
Please sign in to leave a comment.
Comments
0 comments