Providing the content of memory locations in a specific range as a list of rows in a table uses a lot of vertical screen real estate while limiting the displayed range of information quite a bit. Memory examination windows more typically tend to use a grid display, maximizing the screen real estate in terms of providing a clean overview. E.g. displaying data in a grid similar to what 'od' provides on textmode terminals tends to provide for a much better user interaction experience.
Superseeded by bug #4674 *** This bug has been marked as a duplicate of 4674 ***
My most sincere apologies, but how can an older ticket be a duplicate of a newer ticket? Obviously, the newer ticket is the one that duplicates this one. If there is information to share about this issue, please be so kind as to include it here?
Looking closer, this seems to largely be a bit of a dependency problem. May I suggest that this ticket (4623) is set as depending on the split out tasks (4669, 4674, 4675), and that 4623 is set as the blocker for 3119? That shows the dependency. Just closing this one as a duplicate of a ticket about something quite different (label of the number of bits selection) is just confusing.
2007-11-02 Zhao Shujing <pearly.zhao@oracle.com> * memory/MemoryWindow.java: Change the data visualization as a grid display. Fixes #4623. * gladedir/memorywindow.glade: Remove toBox and toSpin.