[#KINECTSDK] Caution when you work with frames! (dispose objects correctly)

Hello!

Some time ago I wrote a post about the importance of properly destroy the objects of the KinectSdk when you close an app. The lesson today is similar, but bounded to work with a Frame.

For example, the following piece of code shows 2 ways of processing a FRAME with KinectSDK V2

The function between lines 1 and 19, used the frame within a using() and 2nd option does not. The strange thing is that the 2nd option does not give an error or anything. However when not destroyed the dmard, it never returns to process a new frame with what the Kinect information process is stopped for this application.

Lesson learned live!

Saludos @ Home

El Bruno

image image image Google
Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.