Skip to content

Conversation

@TheBEber
Copy link

  • Adapting replay speed to recorded scenario
  • Concatenation of TimeElapsed cannot be done as proposed, need to be splitted after another event (to be able to calculate the time during which a button has been pressed, and replay it exactly) (exemple of a jump, when we start/stop pushing a button needs to be exact, in the exemple in the commit message, we may consider the button has been pressed for twice the real time (repends of the implementation for sure...))
  • Gui start state needs to be recorded (windows size/scale & position of internal elements -> saved for now in imgui.ini, but needs to be reset to the state before the start of recording in order to replay it correctly) ( this commit may not be the good way to handle it, but it is more for illustration of the problem)
  • Some bug still exists : mouse clic does not seems to work for windows resize (Resize event to be handled) and internal sub-windows movement/resizing does not seems to work either

bmayeur added 3 commits September 12, 2020 17:42
In the case:

- Button pushed
- TimeElapsed
- Button released
- TimeElapsed
             <--- now the game state knows the button is release
- TimeElapsed
- TimeElapsed
- Something else happened

Otherwise, after compression in replay it would become

- Button pushed
- TimeElapsed
- Button released
- TimeElapsed (compressed, so x3)
             <--- now the game state knows the button is release
- Something else happened

Such that the timings are incorrects
Arguments of the display may have changed between save/replay

Here is some way to do it. Maybe not the best way to, my idea was to expose the problem here.

Another problem that is still not fixed here:

- Windows are not resized / Moved by replay
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant