Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
I
Interactive Wave Simulator
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Model registry
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Pascal Engeler
Interactive Wave Simulator
Commits
7b60562e
Commit
7b60562e
authored
3 years ago
by
Pascal Engeler
Browse files
Options
Downloads
Patches
Plain Diff
a newline
parent
c1a6eec6
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+1
-0
1 addition, 0 deletions
README.md
with
1 addition
and
0 deletions
README.md
+
1
−
0
View file @
7b60562e
...
...
@@ -178,6 +178,7 @@ The application is split into different modules, each module handles a subset of
Much like the name suggests, the
`Toolbox`
is passed around from one module to the next, and each can then access everything stored within it.
Each module can see all information and decide how it reacts to the current combination of state, messages and events (user input).
The logical flow of the application game loop goes as follows:
1.
`InputHandler`
fetches and writes new user input into the
`Toolbox`
event chain
2.
`TimeoutHandler`
checks if there is any user input, and if timeout occurs posts reset requests to the
`Toolbox`
mailbox targeting all other modules
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment