But eventually you started to feel tired or lazy, not wanting to expend so much effort just to change a simple value in your code or add an element to the WPF that would result in about 30 seconds of down time between builds.
Sound familiar? If you’re like me, this process was perfectly OK with you the first dozen or so times you went through it, excitement providing the force to overcome the object at rest (thank you, Sir Isaac Newton). If you just started developing with Kinect, I bet I can predict how you initially added a new feature or experimented with another visual: You eagerly hit F5, jumped out of your seat, moved in front of your Kinect, motioned and gyrated to express what you wanted in your application, ran into a bug or observed something that wasn’t quite what you expected or wanted, sat back down, stopped the application and went back to coding. I hope that those of you who had been hesitating to get a Kinect for Windows and start building applications were encouraged not to wait any longer.
In June I covered the basics of creating a Windows Presentation Foundation (WPF) application that uses Kinect for Windows to track a user’s skeleton and draw it on the screen. Volume 27 Number 09 Kinect - Working with Kinect Studio
0 kommentar(er)
