Closed GoogleCodeExporter closed 8 years ago
I see that we're using gtk entries so users can select the MD5 and other info.
for cutting and pasting, such as into a bug report. This is good to have.
Updated the GUI styles and fixed the comment entry issue in Commit 249.
This brings up why we're not using our CalculateMD5() routine? Is there some
issue
with it I am unaware of? Is this for some future planned use?
I see it loads the ROM into the global ROM memory space. This is bad, since if
a
user was running the emulator and wanted to compute the MD5 of a ROM from the
GUI
the emulator would crash.
Thus we have two options:
1) Have computing the MD5 load the rom and prohibit it while the emulator is
running.
2) Change these functions to load the rom for MD5 computation into a defined
memory
space and specify.
I think #2 is the better option but didn't want to change these core functions
without consulting.
Original comment by sknau...@wesleyan.edu
on 20 Apr 2008 at 8:44
[deleted comment]
Original comment by sknau...@wesleyan.edu
on 20 Apr 2008 at 8:45
Going with #2 as we want to be able to use the same rom handling functions with
the
general rom cache. Also, the rom loading code needs a good cleanup.
Original comment by sknau...@wesleyan.edu
on 9 May 2008 at 12:56
Original comment by sknau...@wesleyan.edu
on 9 May 2008 at 12:56
Original comment by sknau...@wesleyan.edu
on 11 May 2008 at 8:21
Original issue reported on code.google.com by
sknau...@wesleyan.edu
on 20 Apr 2008 at 9:13