new midica version

- updated screenshots - adjusted description to new keybindings
truj · Sep 12, 2023 · dbc3fe2 · dbc3fe2
1 parent 2b180b9
commit dbc3fe2
Show file tree

Hide file tree

Showing 7 changed files with 3 additions and 2 deletions.
diff --git a/src/assets/img/info_about.png b/src/assets/img/info_about.png
diff --git a/src/assets/img/info_keybinding_1.png b/src/assets/img/info_keybinding_1.png
diff --git a/src/assets/img/info_keybinding_2.png b/src/assets/img/info_keybinding_2.png
diff --git a/src/assets/img/info_midi_general.png b/src/assets/img/info_midi_general.png
diff --git a/src/assets/img/main.png b/src/assets/img/main.png
diff --git a/src/assets/img/soundbank_0.png b/src/assets/img/soundbank_0.png
diff --git a/src/pages/tutorial.html b/src/pages/tutorial.html
@@ -131,7 +131,8 @@ <h2>Development Process</h2>
 			</p>
 			<p>
 				During the development process you will switch from your editor to the Midica player very often.
-				You will change the file and save it in the editor, then switch to the player and hit the <code>Reparse</code> button or press <code>F5</code>.
+				You will change the file and save it in the editor, then switch to the player and hit the <code>Reparse</code> button or press <code>F5</code>
+				or <code>Ctrl+R</code> (or <code>Cmd+R</code> if you are on a Mac).
 				Then the file will be parsed again. When hitting the <code>Play</code> button or pressing <code>p</code> or the space bar,
 				the resulting MIDI sequence will be played.
 			</p>
@@ -201,7 +202,7 @@ <h2>Development Process</h2>
 			</p>
 			<p>
 				Developing with Midica is a bit like developing a website. But the HTML editor is any text editor. And the browser is the player.
-				But F5 works similarly.
+				But F5 works similarly. Or <code>Ctrl+R</code> or <code>Cmd+R</code>.
 			</p>
 		</div>
 	</section>