New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hex editor shows wrong "File on Disk" when switching games #3527
Comments
In general, I think calling Other places where those properties are read inside BizHawk/src/BizHawk.Client.EmuHawk/tools/HexEditor/HexEditor.cs Lines 227 to 232 in 15056f1
BizHawk/src/BizHawk.Client.EmuHawk/tools/BasicBot/BasicBot.cs Lines 288 to 292 in 15056f1
BizHawk/src/BizHawk.Client.EmuHawk/tools/MultiDiskBundler/MultiDiskBundler.cs Lines 56 to 90 in 15056f1
All instances of tools reading those properties inside Could also negatively affect external tools. |
Context: these are |
Summary
When loading two different roms while the hex editor is open, the "File on Disk" in the hex edtior will show the contents of the previous rom, rather than the current rom. Additionally, if the previous rom was a MAME archive, an error will occur.
Repro
Alternatively, load a MAME archive at step 2 to reproduce the exception
Output
If the first rom was a MAME archive:
Host env.
Cause
The issue is that
HexEditor.GetRomBytes()
(called fromHexEditor.Restart()
) loads the rom fromMainForm.CurrentlyOpenRomArgs
, butMainForm.LoadRomInternal
callsTools.Restart()
before updatingCurrentlyOpenRomArgs
:BizHawk/src/BizHawk.Client.EmuHawk/tools/HexEditor/HexEditor.cs
Lines 425 to 433 in 1df6ce4
BizHawk/src/BizHawk.Client.EmuHawk/MainForm.cs
Lines 3934 to 3950 in 15056f1
The text was updated successfully, but these errors were encountered: