Menu

#569 prev_frame goes wrong after a reset

Next_release
open
nobody
reverse (8)
5
2015-03-02
2015-03-02
No

Scenario:

  • with reverse enabled, just run a machine for a while
  • reset the machine
  • use prev_frame

This will jump much more than just one frame backwards.

Quick analysis: prev_frame (indirectly) uses "machine_info time", but this time is reset to 0 after the reset command...

Perhaps the reset command shouldn't reset the MSX time? (What else is relying on 'machine_info time' like this? And what might be relying on reset also causing a reset of the machine time?)

Thanks to mth for reporting/noticing this.

Discussion

MongoDB Logo MongoDB