Thanks to all who attended my first session today, and a thank you in advance to those attending Thursday’s session on multi-touch. I’m going to post my slide deck for the What’s New in VS2010 Debugging session now and I will update this post on Thursday/Friday with the source and slides for the multi-touch session. Feel free to contact me with any comments or suggestions, good or bad.
Enjoy!
I have been selected to speak at this year’s VSLive! conference on the Microsoft Campus in Redmond. I’m very excited about this conference for a couple of reasons. First, it’s on campus, which will allow me to get together with my Coding4Fun/Channel 9 friends to do some planning. Secondly, VSLive! attendees are also allowed to spend some of their own cash at the Microsoft store. And finally, in addition to presenting two sessions at the conference, I’m also coordinating a special event on Wednesday night which we’re calling Devopalozza. I am creating a team Jeopardy! style game-show which will pit Microsoft Speakers against VSLive! Speakers against VSLive! Attendees. I’m currently creating both hardware and software to drive the game, which will later turn into an article on Coding4Fun for those that might want to create a game-show at home or the office. And, I’ll even be hosting the show at the event.
The fifth episode of my Coding4Fun Show, is now up on Channel 9. In this episode of the Coding4Fun Show, I chat with Josh Blake about Natural User Interfaces and Multitouch programming with .NET. Josh has written a multitouch PowerPoint replacement called NaturalShow, which was demonstrated during his NUI session at MIX10. Watch and learn a bit about how this application was created as well as how you can write multitouch applications with WPF. And for even more multitouch programming goodness and more on NaturalShow, Josh is currently working on a book titled Multitouch on Windows, which can be purchased and read while he's writing it!
You should see the video below if you have Silverlight installed, otherwise head over to the episode on Channel 9 to watch and download in a variety of formats for offline viewing.
A big thanks to Josh for the interview!
I’ve been working on a version 2.0 of WiimoteLib which reorganizes the library quite a bit to clean up the codebase. It’s not quite ready for release, and I don’t have an ETA currently, but I wanted to note some of the changes and get some feedback as I finish things up.
using System;
using System.Drawing;
namespace WiimoteLib.Extensions
{
public class Nunchuk : ExtensionController<NunchukState>
{
internal Nunchuk(Wiimote wm) : base(wm)
{
}
internal override void Initialize()
{
byte[] buff = Wiimote.ReadData(REGISTER_EXTENSION_CALIBRATION, 16);
State.CalibrationInfo.AccelCalibration.X0 = buff[0];
State.CalibrationInfo.AccelCalibration.Y0 = buff[1];
State.CalibrationInfo.AccelCalibration.Z0 = buff[2];
State.CalibrationInfo.AccelCalibration.XG = buff[4];
State.CalibrationInfo.AccelCalibration.YG = buff[5];
State.CalibrationInfo.AccelCalibration.ZG = buff[6];
State.CalibrationInfo.MaxX = buff[8];
State.CalibrationInfo.MinX = buff[9];
State.CalibrationInfo.MidX = buff[10];
State.CalibrationInfo.MaxY = buff[11];
State.CalibrationInfo.MinY = buff[12];
State.CalibrationInfo.MidY = buff[13];
}
internal override void ParseData(byte[] buff, int offset)
{
State.RawJoystick.X = buff[offset];
State.RawJoystick.Y = buff[offset + 1];
State.AccelState.RawValues.X = buff[offset + 2];
State.AccelState.RawValues.Y = buff[offset + 3];
State.AccelState.RawValues.Z = buff[offset + 4];
State.C = (buff[offset + 5] & 0x02) == 0;
State.Z = (buff[offset + 5] & 0x01) == 0;
State.AccelState.Values.X = (float)((float)State.AccelState.RawValues.X - State.CalibrationInfo.AccelCalibration.X0) /
((float)State.CalibrationInfo.AccelCalibration.XG - State.CalibrationInfo.AccelCalibration.X0);
State.AccelState.Values.Y = (float)((float)State.AccelState.RawValues.Y - State.CalibrationInfo.AccelCalibration.Y0) /
((float)State.CalibrationInfo.AccelCalibration.YG - State.CalibrationInfo.AccelCalibration.Y0);
State.AccelState.Values.Z = (float)((float)State.AccelState.RawValues.Z - State.CalibrationInfo.AccelCalibration.Z0) /
((float)State.CalibrationInfo.AccelCalibration.ZG - State.CalibrationInfo.AccelCalibration.Z0);
if(State.CalibrationInfo.MaxX != 0x00)
State.Joystick.X = (float)((float)State.RawJoystick.X - State.CalibrationInfo.MidX) /
((float)State.CalibrationInfo.MaxX - State.CalibrationInfo.MinX);
if(State.CalibrationInfo.MaxY != 0x00)
State.Joystick.Y = (float)((float)State.RawJoystick.Y - State.CalibrationInfo.MidY) /
((float)State.CalibrationInfo.MaxY - State.CalibrationInfo.MinY);
}
public override ExtensionType ExtensionType
{
get { return ExtensionType.Nunchuk; }
}
}
/// <summary>
/// Current state of the Nunchuk extension
/// </summary>
[Serializable]
[DataContract]
public class NunchukState : IExtensionState
{
/// <summary>
/// Calibration data for Nunchuk extension
/// </summary>
[DataMember]
public NunchukCalibrationInfo CalibrationInfo;
/// <summary>
/// State of accelerometers
/// </summary>
[DataMember]
public AccelState AccelState;
/// <summary>
/// Raw joystick position before normalization. Values range between 0 and 255.
/// </summary>
[DataMember]
public Point RawJoystick;
/// <summary>
/// Normalized joystick position. Values range between -0.5 and 0.5
/// </summary>
[DataMember]
public PointF Joystick;
/// <summary>
/// Digital button on Nunchuk extension
/// </summary>
[DataMember]
public bool C, Z;
}
/// <summary>
/// Calibration information stored on the Nunchuk
/// </summary>
[Serializable]
[DataContract]
public struct NunchukCalibrationInfo
{
/// <summary>
/// Accelerometer calibration data
/// </summary>
public AccelCalibrationInfo AccelCalibration;
/// <summary>
/// Joystick X-axis calibration
/// </summary>
[DataMember]
public byte MinX, MidX, MaxX;
/// <summary>
/// Joystick Y-axis calibration
/// </summary>
[DataMember]
public byte MinY, MidY, MaxY;
}
}
Minimal changes will need to be handled in application code, which is demonstrated in the WiimoteTest application included with the library. The biggest change is in handling extensions. Now, the Wiimote object itself will contain an ExtentionType property. Use this to determine which extension is attached and cast the Wiimote.ExtensionController property to the proper object to access its state information as shown:
As I posted earlier, I’ll be attending MIX10 this year, and I will be taking part in the Ask the Experts panel on Monday evening at 5pm. I will be at the C# table since I’m a C# MVP, so stop by and start a discussion! Experts in a variety of subjects will be on hand so even if C# isn’t your thing, surely one of the many other topics will be. And even if you’re an antisocial shut-in like I am, beer will be served and there will be 2 Zune HDs given away to attendees of the event. So really, there’s something for everyone. Hope to see you there!