Forum Discussion
MessageHandler and message order
Did you guys play around with the MessageHandler yet, maybe have implemented your own?
My understanding so far is, that with a MessageHandler, one is able to intercept events such as the device being added and / or removed from the system.
I'm curious about the content and order of appearance OVR::MessageDeviceStatus. Assuming you have installed a filter on OVR::DeviceManager, do two separate messages arrive, one for the sensor and one for the HMD? If so, in which order to they arrive? If not, which message does arrive, if any? I'm also curious about the reverse, e.g. removing the rift from the system and the messages which arrive under those circumstances.
If some of you would like to help me find this out (my devkit has not arrived yet), then I'll write a small sample which should track the order and occurence of those messages, so you can run it.
My understanding so far is, that with a MessageHandler, one is able to intercept events such as the device being added and / or removed from the system.
I'm curious about the content and order of appearance OVR::MessageDeviceStatus. Assuming you have installed a filter on OVR::DeviceManager, do two separate messages arrive, one for the sensor and one for the HMD? If so, in which order to they arrive? If not, which message does arrive, if any? I'm also curious about the reverse, e.g. removing the rift from the system and the messages which arrive under those circumstances.
If some of you would like to help me find this out (my devkit has not arrived yet), then I'll write a small sample which should track the order and occurence of those messages, so you can run it.
2 Replies
- The sensor and display have two separate cables. I'm going to go out on a limb and say you get the messages in the order they are connected/disconnected.
- I totally forgot that. Yes, that would make sense. It think i I'll operate under this assumption for now, seems reasonable.
