178
edits
(→Add events recording: grammar and such) |
|||
Line 297: | Line 297: | ||
If you don't have any of the required games, there are several [http://www.scummvm.org/demos.php demos] available. A 16bit graphics demo example would be the [http://quick.mixnmojo.com/demos/ffcovedemo.zip Freddi5 demo]. | If you don't have any of the required games, there are several [http://www.scummvm.org/demos.php demos] available. A 16bit graphics demo example would be the [http://quick.mixnmojo.com/demos/ffcovedemo.zip Freddi5 demo]. | ||
=== Add | === Add event recording === | ||
''Technical Contact'': [[User:Sev|Eugene Sandulenko]], [[User:Fingolfin|Max Horn]] | ''Technical Contact'': [[User:Sev|Eugene Sandulenko]], [[User:Fingolfin|Max Horn]] | ||
''Background:'' | ''Background:'' | ||
All engines in ScummVM are driven by 3 streams of external | All engines in ScummVM are driven by 3 streams of external influences: | ||
* Mouse moves | * Mouse moves | ||
* Keyboard events | * Keyboard events | ||
* Pseudo random number generators | * Pseudo-random number generators | ||
It would be | It would be useful to have some layer in between our system-dependent backends and engines which can record these events to a file and can play them back later. | ||
This will significantly help with regression testing. | This will significantly help with regression testing. | ||
The solution should be high-level, perhaps in form of a custom event loop, so all engines will be able to use it with minimal | The solution should be high-level, perhaps in the form of a custom event loop, so that all engines will be able to use it with minimal effort. | ||
== Implement "return to launcher" feature == | == Implement "return to launcher" feature == |
edits