{"issue":{"pull_request":{"diff_url":null,"html_url":null,"patch_url":null},"state":"open","user":{"avatar_url":"https://secure.gravatar.com/avatar/3b0860ec0180f7fb7ac4d2cd9252ec3f?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"3b0860ec0180f7fb7ac4d2cd9252ec3f","url":"https://api.github.com/users/ofTheo","login":"ofTheo","id":144000},"milestone":null,"assignee":null,"labels":[],"updated_at":"2011-10-31T15:41:55Z","closed_at":null,"comments":5,"url":"https://api.github.com/repos/ofTheo/ofxKinect/issues/81","body":"the old clipping method set pixels closer than minClip to 0 - the new approach setDepthClipping sets minClip to 255. \r\nsetDepthClipping implies clipping of the data . \r\n\r\nwould be great if it defaulted to the previous approach - or at least had an option to toggle whether minClip is 255 or 0 \r\n\r\n\r\n","html_url":"https://github.com/ofTheo/ofxKinect/issues/81","title":"setDepthClipping - should allow for < minClip = 0","number":81,"id":2097954,"created_at":"2011-10-31T15:16:19Z"},"action":"created","comment":{"user":{"avatar_url":"https://secure.gravatar.com/avatar/5fa1d3aa502b308b8a3ae814fb88ac04?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"5fa1d3aa502b308b8a3ae814fb88ac04","url":"https://api.github.com/users/danomatika","login":"danomatika","id":480637},"updated_at":"2011-10-31T15:41:55Z","url":"https://api.github.com/repos/ofTheo/ofxKinect/issues/comments/2578551","body":"Hrm. Running the example returns 0's when my hand comes too close ... a hole is created. Is this not supposed to happen? Setting this to anything other then 0 dosen't make sense since how can we tell the difference between near and far noise/out of range values?","id":2578551,"created_at":"2011-10-31T15:41:55Z"}}