Search found 7 matches
- Thu Mar 17, 2016 9:17 am
- Forum: Developer's Forum for Windows
- Topic: Multiple devices not getting SI_SKIP_EVENT
- Replies: 7
- Views: 12619
Re: Multiple devices not getting SI_SKIP_EVENT
It's counter-intuitive that any call to SiGrabDevice would change the behavior of SiGetEvent in any way. I was calling SiGrabDevice like so: SiGrabDevice( device.handle, SPW_TRUE ) Changing that to: SiGrabDevice( device.handle, SPW_FALSE ) ... fixed my message pump. I had wanted an exclusive claim o...
- Wed Mar 16, 2016 4:25 pm
- Forum: Developer's Forum for Windows
- Topic: Multiple devices not getting SI_SKIP_EVENT
- Replies: 7
- Views: 12619
Re: Multiple devices not getting SI_SKIP_EVENT
I've discovered that changing my call to SiGrabDevice to use "soft capture" causes SiGetEvent to only return SI_IS_EVENT when the passed device handle matches the originating device. This is how I had expected it to work in the first place, and it allows me to correctly identify the origin...
- Wed Mar 16, 2016 11:55 am
- Forum: Developer's Forum for Windows
- Topic: Multiple devices not getting SI_SKIP_EVENT
- Replies: 7
- Views: 12619
Re: Multiple devices not getting SI_SKIP_EVENT
ok, thanks for the info about SI_SKIP_EVENT. I had assumed it would be returned if I called SiGetEvent on a message that was not associated with the passed handle. Based on the documentation: "If SiGetEvent returns a value of SI_SKIP_EVENT, this indicates the event is indeed a 3DxWare event, bu...
- Tue Mar 15, 2016 12:55 pm
- Forum: Developer's Forum for Windows
- Topic: Multiple devices not getting SI_SKIP_EVENT
- Replies: 7
- Views: 12619
Multiple devices not getting SI_SKIP_EVENT
I have multiple devices almost working. I create a hidden window on a secondary thread, and open the devices on that thread. I have verified that I can open two devices, each has a different SiHdl address, and device id. I can address the LED on each device independently. The only issue is that SiGe...
- Fri Mar 04, 2016 4:51 pm
- Forum: Developer's Forum for Windows
- Topic: Device taking over Esc key, handle button presses in code
- Replies: 2
- Views: 8142
Re: Device taking over Esc key, handle button presses in cod
Sorry, just answering all my own questions. There doesn't appear to be a way to delete a topic. For future reference, I created a hidden window that's a child of my main window so that the 3DConnexion device has a dedicated message queue. I grab the device so that the hidden window has exclusive acc...
- Fri Mar 04, 2016 2:49 pm
- Forum: Developer's Forum for Windows
- Topic: Device taking over Esc key, handle button presses in code
- Replies: 2
- Views: 8142
Re: Device taking over Esc key, handle button presses in cod
ouch, ok, I blindly copied the example's while loop, which was 90% of the problem. Embarrassing.
The only remaining issue I have is correctly getting the device's button events to be handled in the application code using SiSyncSetButtonAssignment.
The only remaining issue I have is correctly getting the device's button events to be handled in the application code using SiSyncSetButtonAssignment.
- Fri Mar 04, 2016 12:47 pm
- Forum: Developer's Forum for Windows
- Topic: Device taking over Esc key, handle button presses in code
- Replies: 2
- Views: 8142
Device taking over Esc key, handle button presses in code
Hi, I'm having a few issues integrating a SpaceNavigator with Cinder ( https://libcinder.org/ ). First, using the driver seems to take over the application's update loop. I'm not super familiar with Windows application programming, so I can't say for sure what's causing it, but it happens once I cal...