Search found 4 matches

by Ambroise
Wed May 16, 2007 4:59 am
Forum: Developer's Forum for Windows
Topic: COM event handler not called
Replies: 7
Views: 19459

That must definitely be the cause for our issue: our 3Dconnexion support plug-in can be loaded either at application startup (while a splash screen is displayed) or later from a modal dialog. In both cases, the top-level window is distinct from the application main window and is closed shortly after...
by Ambroise
Wed May 16, 2007 1:27 am
Forum: Developer's Forum for Windows
Topic: COM event handler not called
Replies: 7
Views: 19459

Hi, There is indeed a splash screen that is displayed while the COM object is created (however, hooking handlers and connecting to the driver happens after the splash screen is closed). I went back to my previous computer and I noticed it was running 3DxWare 3.2.2 (while the new machine has 3.3.2 in...
by Ambroise
Tue May 15, 2007 8:51 am
Forum: Developer's Forum for Windows
Topic: COM event handler not called
Replies: 7
Views: 19459

Thank you for your quick reply. I have made further tests today and I found out that this is not linked to the dual core CPU, since the software also fails on Pentium 4 machines like the one it used to be working on. I keep investigating... I will try to find a backup of the application that was com...
by Ambroise
Mon May 14, 2007 8:55 am
Forum: Developer's Forum for Windows
Topic: COM event handler not called
Replies: 7
Views: 19459

COM event handler not called

Hello, After using the COM SDK to add 3Dconnexion device support to our non-COM, single-threaded, wxWidgets-based application, I had a completely working prototype. However, I switched to a new computer last week and since then, although I can connect to the driver, hooked event handlers are never c...