-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DeviceEvent.{CONNECTED, DISCONNECTED} not dispatched #22
Comments
We have the same problem, our application (with two kinects connected) will be running all day in a museum and sometimes a kinect will disconnect, and we can't reconnect it without resetting the whole application. We think the problem lays here, please advice. |
Will look into this. Probably windows SDK only, as I haven't figured it out to get the connected event working with openni 1.x |
We're on windows using the windows sdk ane, we haven't tried the openni sdk. What do you do to restart kinects if they somehow fail during the run of an application? |
Any progress with this issue?? |
Hi guys, any news about the DeviceEvent not dispatched ? I can detect a newly connected Kinect with Microphone.getMicrophone, but i have no way to run the MSKinnectDevice and to start a new Kinect device Thanks |
I can't get the DeviceEvent.CONNECTED nor the DeviceEvent.DISCONNECTED dispatched and so Kinect.numDevices and Kinect.isSupported values are never being refreshed.
The only way to check correctly each time if there is a Kinect device connected to a USB port is to exit the AIR application and launch it again in order to reset the values.
The text was updated successfully, but these errors were encountered: