Open you program in Dependency Walker and see if there are any missing dependencies: http://www.dependencywalker.com/

It's odd that it's failing, but the control panel works fine. Could be a 32-bit issue.

-Patrick

Hi Patrick I tried your suggestion but with no success, I'm still getting the same error. The error message appears and has to be closed three times when the app is started. The app opens briefly and then closes. Do you have ...

Try copying phidget21.dll and phidget21.net.dll into the same folder as your program - make sure you choose the right phidget21.dll (x86 or x64) depending on if your program is 32-bit or 64-bit.

I'm not sure why it isn't picking up on the installed library.

-Patrick

Yes, we don't support secure websocket directly from our network server - you would need to proxy the websocket traffic yourself - whether this is actually feasible depends on your environment. Another option could be to run the Phidget code server-side rather than client-side, using Node.

-Patrick

... to connect(), or an entry in options to the constructor. As for open - you just call it without the timeout to get this behaviour as Fraser said. -Patrick

you probably need to add -lm to your gcc line to include the math library.

-Patrick

Hi,

This is still on the todo list but I don't know when it will be ready. I'll post here if we have updates in the future.

-Patrick

The queue is per-channel.

-Patrick

That's right, the assembly version has always been set properly, but a quirk in how the nuget version of the assemblies was being built failed to set the file version to match the assembly version. The version installed by our .msi does have that file version set properly.

-Patrick

... device is predictable when you open it. We may in future offer an API to disable this functionality, to make phidget22 more like phidget21." Patrick, Any updates or place I could monitor for "We may in future offer an API to disable this functionality"?