Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
08121 Interface Minor Always 30 days ago 28 days ago
Tester ozfalcon View Status Public Platform SDLMAME
Assigned To cuavas Resolution Fixed OS Linux (64-bit)
Status [?] Resolved Driver
Version 0.237 Fixed in Version 0.238 Build 64-bit
Fixed in Git Commit d64ea53 Github Pull Request #
Summary 08121: UI: Mame UI doesn't realize the machine has started
Description Using the new feature - Break into menu before machine fully starts.
Press TAB at warning screen and the menu opens as expected.
(The machine is suspended & menu shows Start Machine option).

Press TAB again, The menu closes and the machine proceeds to run.

If you press TAB once more, The Menu opens and it still shows Start Machine,
while the expected Select New Machine / Return to Machine is not displayed.
(The machine is clearly running at this point, But the UI doesn't realize it).
Steps To Reproduce Press TAB at warning screen and the menu opens as expected.
(The machine is suspended & menu shows Start Machine option).

Press TAB again, The menu closes and the machine proceeds to run.

If you press TAB once more, The Menu opens and it still shows Start Machine,
while the expected Select New Machine / Return to Machine is not displayed.
(The machine is clearly running at this point, But the UI doesn't realize it).
Additional Information
Github Commit
Flags
Regression Version
Affected Sets / Systems UI
Attached Files
 
Relationships
There are no relationship linked to this issue.
Notes
2
User avatar
No.19399
Tafoid
Administrator
29 days ago
Very minor issue which should be able to be fixed soon. Just click/select "Start Machine" (which since you TAB started the machine, will not restart it again) to obtain the proper TAB menu items.
User avatar
No.19402
cuavas
Administrator
29 days ago
It may appear to be minor, but due to the incredibly bad design of the menu code it actually requires a large amount of refactoring to fix. However, it happens to be the same refactoring required to address a few other issues, so it will be fixed relatively soon.