whoops

author: DaveHodder67 <dave.hodder@focusrite.com> 2015-08-13 18:05:50 +0100
committer: DaveHodder67 <dave.hodder@focusrite.com> 2015-08-13 18:05:50 +0100
commit: d43a3275cccbdbb578866ab117118712bc612dc6 (patch)
tree: 36cd0d5822a3b56d89d50879d9356b34770a221e
parent: 4b985f67fd4fff6211aededd61c28553b066fa01 (diff)
download: launchpad-polymaker-d43a3275cccbdbb578866ab117118712bc612dc6.tar.gz
launchpad-polymaker-d43a3275cccbdbb578866ab117118712bc612dc6.zip
1 files changed, 2 insertions, 2 deletions
diff --git a/README.md b/README.md
index f91b06b..322fef1 100644
--- a/README.md
+++ b/README.md
@@ -96,12 +96,12 @@ Instead, you're going to have to do things the old fashioned way - by blinking L
 If do you want to debug interactively (and of course you do), you can use the interactive desktop simulator on OS X.  
-1. Build the Xcode project located in `/tools/simulator`
+1. Build the Xcode project located in `/tools/osx`
 2. Connect your Launchpad Pro
 3. Install the factory firmware on your Launchpad Pro
 4. Debug away!
-Currently it only supports button presses and LED messages - there's no virtual MIDI output or aftertouch yet.  It has a really awful busywaiting timer for the 1kHz tick.  However, it does allow you to debug your application logic very nicely using Xcode!
+Currently it only supports button presses and LED messages - there's no virtual MIDI IO or aftertouch (yet).  It has a really awful busywaiting timer for the 1kHz tick.  However, it does allow you to debug your application logic using Xcode!
 You can also use the simple command-line simulator located in the `/tools` directory.  It is compiled and ran as part of the build process, so it serves as a very basic test of your app before it is baked into a sysex dump - more of a test harness.
author	DaveHodder67 <dave.hodder@focusrite.com>	2015-08-13 18:05:50 +0100
committer	DaveHodder67 <dave.hodder@focusrite.com>	2015-08-13 18:05:50 +0100
commit	d43a3275cccbdbb578866ab117118712bc612dc6 (patch)
tree	36cd0d5822a3b56d89d50879d9356b34770a221e
parent	4b985f67fd4fff6211aededd61c28553b066fa01 (diff)
download	launchpad-polymaker-d43a3275cccbdbb578866ab117118712bc612dc6.tar.gz launchpad-polymaker-d43a3275cccbdbb578866ab117118712bc612dc6.zip

diff --git a/README.md b/README.md index f91b06b..322fef1 100644 --- a/README.md +++ b/README.md
@@ -96,12 +96,12 @@ Instead, you're going to have to do things the old fashioned way - by blinking L
96		96
97	If do you want to debug interactively (and of course you do), you can use the interactive desktop simulator on OS X.	97	If do you want to debug interactively (and of course you do), you can use the interactive desktop simulator on OS X.
98		98
99	1. Build the Xcode project located in `/tools/simulator`	99	1. Build the Xcode project located in `/tools/osx`
100	2. Connect your Launchpad Pro	100	2. Connect your Launchpad Pro
101	3. Install the factory firmware on your Launchpad Pro	101	3. Install the factory firmware on your Launchpad Pro
102	4. Debug away!	102	4. Debug away!
103		103
104	Currently it only supports button presses and LED messages - there's no virtual MIDI output or aftertouch yet. It has a really awful busywaiting timer for the 1kHz tick. However, it does allow you to debug your application logic very nicely using Xcode!	104	Currently it only supports button presses and LED messages - there's no virtual MIDI IO or aftertouch (yet). It has a really awful busywaiting timer for the 1kHz tick. However, it does allow you to debug your application logic using Xcode!
105		105
106	You can also use the simple command-line simulator located in the `/tools` directory. It is compiled and ran as part of the build process, so it serves as a very basic test of your app before it is baked into a sysex dump - more of a test harness.	106	You can also use the simple command-line simulator located in the `/tools` directory. It is compiled and ran as part of the build process, so it serves as a very basic test of your app before it is baked into a sysex dump - more of a test harness.
107		107