Memory Pane

[CTalkobt]

1. Memory is read-only in the GUI: There is no way to edit a memory cell; the user must switch to the Console and use the poke command (if it exists) or load a file. Hex editors typically allow in-place editing.

   • Suggestion: Allow double-click on a hex cell to open an inline editor.

2. Multiple views have no labels: All four memory panes are titled "Memory 1"–"Memory 4" with no way to set a meaningful name (e.g., "Zero Page", "Stack", "I/O Area").

   • Suggestion: Allow user to rename each memory pane via a double-click on its tab title.

3. No highlighting of recently changed bytes: Unlike the Registers pane which highlights changed values in red, the Memory pane has no diff coloring. When stepping through code it is hard to see what was written.

   • Suggestion: Track last-cycle writes (already tracked by Snap Diff) and highlight changed bytes in the memory view for one refresh cycle.

4. Page Up/Down scrolls by 256 bytes, not by a visual page: The virtual list has 4096 rows (all 64 KB), so "page" should mean the number of visible rows. Scrolling by 256 bytes (16 rows) when the pane is tall enough to show 30+ rows means the user loses context.

   • Suggestion: Scroll by the number of visible rows (get GetCountPerPage()) not a fixed 256 bytes.

5. No "follow" option: No mode to keep the memory view centered on the current PC, SP, or any register value.

   • Suggestion: Add a "Follow" dropdown (PC / SP / None) in the toolbar.

6. ASCII column uses standard ASCII, not PETSCII: 6502 programs targeting Commodore hardware use PETSCII. All text appears garbled in the ASCII column.

   • Suggestion: Add a character set selector (ASCII / PETSCII / none) in the toolbar per memory view.