Long initialization with no navigator attached.

Post questions, comments and feedback to our 3Dconnexion Windows Development Team.

Moderator: Moderators

Post Reply
slompf
Posts: 5
Joined: Mon Aug 25, 2008 11:24 pm

Long initialization with no navigator attached.

Post by slompf »

Hi,

we are using a 3dnavigator from a application programmed in c#. We discovered, that the initialization with

device = new TDx.TDxInput.Device();

takes about 5 seconds if the driver is installed, but no navigator is attached. Is there a possibility to check for connection before initialization or get rid of this time in another way?

Best regards
tg
jwick
Moderator
Moderator
Posts: 3359
Joined: Wed Dec 20, 2006 2:25 pm
Location: USA
Contact:

Post by jwick »

Hi tg,

The best thing would be to put the initialization into another thread, so your main thread won't get delayed.

A worse alternative would be to check for a window the driver creates. This would tell you if there is a driver running. No window, no driver, no device. If you don't find the window, don't call any TDxInput methods. This is worse because it ties you to an implementation detail of TDxInput; it is currently hosted by the 3DxWare driver...but in the future it may not be. The window class name to look for is "SpaceWare Driver Class"...but I don't recommend it.

The next major driver release resolves this delay. Sorry, I can't tell you when that is.

Jim
3Dx Software Development
slompf
Posts: 5
Joined: Mon Aug 25, 2008 11:24 pm

Post by slompf »

Ok, thank you.
Post Reply