- --
Viewing Issue Advanced Details
[ Jump to Notes ]
ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
---|---|---|---|---|---|
03466 | Interface | Feature | Always | Oct 5, 2009, 21:01 | Oct 6, 2009, 12:01 |
Tester | Tafoid | View Status | Public | Platform | MAME (Self-compiled) |
Assigned To | aaron | Resolution | Fixed | OS | Windows 2000 |
Status [?] | Resolved | Driver | |||
Version | 0.134u2 | Fixed in Version | 0.136 | Build | Normal |
Fixed in Git Commit | Github Pull Request # | ||||
Summary | 03466: Enhancements to -watchdog command | ||||
Description |
I was using the -watchdog function recently and noticed a couple things about it's function that could stand improvement. 1) Start -watchdog timer after the emulation starts Currently, the -watchdog timer starts immediately upon starting MAME. This includes the time where you have to navigate warning/information windows or even loading the roms - the clock is ticking. It's my opinion that since loading a romset is not same across all games, it would be better to start the count just as the emulation begins, rather then immediately. Also, starting it at emulation start would better sync with other timer-based command such as -seconds_to_run. 2) Leave a message (fatalerror) when MAME has stopped due to this watchdog. A simple message detailing the fact that MAME was shutdown due to watchdog time elapsing would be sufficient. Right now, you simply get dropped out of MAME without any special message identifying the reason. |
||||
Steps To Reproduce | |||||
Additional Information | |||||
Github Commit | |||||
Flags | |||||
Regression Version | |||||
Affected Sets / Systems | |||||
Attached Files
|
|||||
Relationships
There are no relationship linked to this issue. |
Notes
1
No.05011
etabeta Developer
Oct 6, 2009, 12:01
|
not sure about what aaron thinks about these, but they sound reasonable requests |
---|