RAM Watch shows inaccurate values

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Open BizHawk 1.6.1 and pause the emulation
2. Open "Dodge 'em (1980) (Atari).a26"
3. Open the Hex Editor
2. Open the RAM Watch file that is attached
3. Advance 1 frame.  Notice that the RAM Watch still shows all values as 00, 
though the Hex Editor shows that the RAM has been initialized
4. Click inside the RAM Watch window

What is the expected output? What do you see instead?
The RAM Watch values change once you click inside the window.  Once you do 
this, they are equal to the values shown in Hex Editor.  Although, they should 
already be equivalent before clicking  inside the RAM Watch window.

What version of the product are you using? On what operating system?
BizHawk 1.6.1 on Windows XP SP3

Original issue reported on code.google.com by shermil...@gmail.com on 18 Apr 2014 at 6:40

Attachments:

• [Dodge 'em (1980) (Atari).wch](https://storage.googleapis.com/google-code-attachments/bizhawk/issue-156/comment-0/Dodge 'em (1980) (Atari).wch)

[GoogleCodeExporter]

Original comment by adeli...@tasvideos.org on 25 Apr 2014 at 7:43

• Added labels: Milestone-Release1.7, Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Original comment by adeli...@tasvideos.org on 25 Apr 2014 at 8:03

• Changed state: Fixed
• Added labels: ****
• Removed labels: ****