You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the driver is running everything is fine. But if not, it just hangs my program indefinitely (prints a, but never b).
(ps: the 'somedevice.comif' is correct, because if I put in some random value I get a proper error that a class with this name does not exist)
I don't know if it's a Problem with the driver I'm using (more likely, but unfortunately I have no control over this one) or with this package.
Would be great if the COM initialization could be made asynchronous, or I'm able to pass some 'timeout' option to the constructor call, so I can deal with this and not just stuck my whole application.
The text was updated successfully, but these errors were encountered:
Hi,
Thanks for the great project.
I'm using this package to communicate with a device-driver. In my logic I'm calling (default settings from readme):
If the driver is running everything is fine. But if not, it just hangs my program indefinitely (prints a, but never b).
(ps: the 'somedevice.comif' is correct, because if I put in some random value I get a proper error that a class with this name does not exist)
I don't know if it's a Problem with the driver I'm using (more likely, but unfortunately I have no control over this one) or with this package.
Would be great if the COM initialization could be made asynchronous, or I'm able to pass some 'timeout' option to the constructor call, so I can deal with this and not just stuck my whole application.
The text was updated successfully, but these errors were encountered: