The intiface-cli-node from intiface

intiface-cli-node's People

Contributors

Stargazers

Watchers

intiface-cli-node's Issues

Linux intiface desktop doesn't use localhost name

See intiface/intiface-tutorial#7 (comment)

CLI not relaying connection information

Connecting from something like playground, a successful connection doesn't update the Intiface Desktop GUI. GUI still shows disconnected, with no client name.

Connecting and disconnecting to the same process multiple times causes event emitter leak warnings

Server using string based output.
Starting insecure websocket server
Insecure server listening on port 12345
(node:11037) UnhandledPromiseRejectionWarning: Error: WebSocket is not open: readyState 2 (CLOSING)
    at WebSocket.send (/snapshot/intiface-cli-node/node_modules/ws/lib/websocket.js:329:19)
    at WebSocketServer.<anonymous> (/snapshot/intiface-cli-node/node_modules/buttplug-node-websockets/dist/src/ButtplugNodeWebsocketServer.js:122:32)
    at Generator.next (<anonymous>)
    at fulfilled (/snapshot/intiface-cli-node/node_modules/buttplug-node-websockets/dist/src/ButtplugNodeWebsocketServer.js:11:58)
    at process._tickCallback (internal/process/next_tick.js:68:7)
(node:11037) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:11037) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
^CShutting down
Stopping websocket server

Device config argument tries to send file path to buttplug

Buttplug.DeviceConfigurationManager.LoadFromJsonExternalConfig() expects a json string, not a file path. We should try to load the file before sending it to buttplug.