Hot on the heels of the Kinect SDK, Microsoft Research is releasing another software development kit (SDK) for a Microsoft natural user interface product. This time, developers will get to tinker with the multi-touch functionality of the (yet-to-be-released) Microsoft Touch Mouse.
The 32bit/64bit SDK includes both C# and C++ code samples consuming the Microsoft TouchMouseSensor API which outputs a 13×15 grayscale pixel sensor image from the integrated sensor of the mouse itself. Third party developers can then use this image to detect gestures and other multi-touch events.
Although the tiny sensor and non-commercial license will limit the scope of third-party uses for this device, but making available an SDK even before the product’s launch is a notable effort to allow developers to experiment with NUI computing without resorting to brute-force hacks.
Update: Even though Microsoft Research removed the Touch Mouse SDK shortly after I wrote about it, Marco of daliz.info found an interesting test tool included in the latest version of IntelliPoint Pro that shows some nice touch sensor visualizations that might help form the basis of a third-party hack for the Touch Mouse.
As PocketNow noted in their Windows Phone Mango preview, the new and much anticipated turn-by-turn feature in Bing Maps has a big asterisks that most people are probably not aware of – it requires constant tapping of the screen to activate voice guidance of the next turn.
Restrictions on your use: We do have some restrictions on your use of the service. You may not:
- present or alert an end user to individual maneuvers of a route in any way that is synchronized with the end-user’s sensor-based position along the route, (e.g. “real-time” navigation);
Until then, the workaround the Windows Phone team has implemented is simple and effective. Tap the screen anywhere to hear the next turn. Audio alerts will also prompt when you’ve made a correct and incorrect turn. Having said that, users should still be wary of local traffic laws which may disallow any interactions with the device while driving.
As Microsoft products make the trip across the Pacific, it’s not unusual for features to get lost at sea. After Windows Phone Mango Beta 2 ROM bits were released to the wild yesterday, a quick headcount reveals a surprising number of features that survived the journey – including both RTM and new Mango features.
Here’s what works in the current Mango build when the system region is set to English (United Kingdom) and search region is set to English (Australia) like the default without the region hack.
- Improved: Speech recognition now supports the full function set (calling, texting, Bing search)
- Improved: Bing Maps now shows local search listings (e.g. Bunnings) with basic information (address search still tend to default to UK, add state or “Australia” to search to lock to Australia)
- New: Bing Local Scout works
- New: Bing Maps directions works with tap-by-tap voice guidance including street names (with British pronunciations)
- New: Bing Local search works (pivot in Bing)
- New: Bing Vision works (with conditions, below)
- New: Speech-to-text and text-to-speech text messaging works
Of course there’s still a few features which fell overboard.
- Crippled: Bing Vision does not scan books, CDs or DVDs (only text, QR codes and Microsoft Tag)
- Crippled: Bing Maps local listings does not show reviews
- Missing: Bing Music Search
- Missing: Bing Quickcards (go to IMDB app)
Together with the possibility that the Zune collection and Zune Pass will finally see the light of day outside of the US, Mango is finally going to set things straight for Australians and many other countries around the world. There’s still room for improvement but the wins easily outweigh the loss.
P.S. The developer Mango beta NDA agreement has since been corrected to allow for public disclosure and screenshots.