https://www.3dconnexion.com/forum/viewtopic.php?t=2301
I thought there was some more discussion on the thread, but I don't know what happened to it.
I never solved the issue, but the flexibility of working with the windows API was worth the quirks that were introduced by using it.
I have gotten to the bottom of an intermittent issue we've been having so I can finally replicate it. While in a standard message loop for a created window launched from inside of UG:
Code: Select all
while (bRet = GetMessage(&msg,NULL,0,0 ) != 0 )
{
TranslateMessage(&msg);
DispatchMessage(&msg);
}
I've trying filtering the messages out of the message loop and a few other things to no avail.
Is there anywhere the interface between the device and NX is documented that I can look through? Does anyone know why this would happen or how to prevent it?