4. Practical examples: Difference between revisions
No edit summary |
No edit summary |
||
| Line 10: | Line 10: | ||
Remember to click on the interface header before giving commands, | |||
the operating System needs to know where the keyboard signals are directed. | the operating System needs to know where the keyboard signals are directed. | ||
<code>backspace</code> starts the patch and selects the LiveEditor Tab. | |||
<code>spacebar</code> (6 times at least) to set up a tap tempo | |||
<code>1</code>> Sets the render opacity to 0 | |||
<code>2</code>> Sets the render opacity to 0.5 | |||
<code>3</code> Sets the render opacity to 1 | |||
<code>4</code> Writes Output informations on the Javascript console. | |||
Takes a screenshot of the output and saves it in "C:\screen" | |||
(if the directory already exists) | |||
Revision as of 14:22, 7 December 2022
Download the Javascript Reference folder from https://www.mxwendler.net/de/downloads.html
1) Double click on the "js-demo.mxw" to load the demo.
2) Open the I/O window (CTRL+1) or Menu: Settings, I/O Midi, Keyboard...
- click on SHOW JAVASCRIPT CONSOLE, almost at the bottom of the I/O window.Commands:
Remember to click on the interface header before giving commands, the operating System needs to know where the keyboard signals are directed.
backspace starts the patch and selects the LiveEditor Tab.
spacebar (6 times at least) to set up a tap tempo
1> Sets the render opacity to 0
2> Sets the render opacity to 0.5
3 Sets the render opacity to 1
4 Writes Output informations on the Javascript console.
Takes a screenshot of the output and saves it in "C:\screen"
(if the directory already exists)