qDot

Results 224 issues of qDot

Spent a long time making sure everything async passes stuff, but we don't actually have any examples or tests of passing tokens and stopping stuff. Should actually do that.

library

Implement a way for disconnect to tear down protocols before devices (so we can do things like box resets, this would also be nice to make sure we stop devices...

hardware support
server

Implement timeouts in ReadValueAsync (probably useful everywhere, can work at Device level in ButtplugDeviceImpl again, just use cancellation tokens and timers)

hardware support
server

Easier than having the user try and figure it out themselves, we can just have them send a log.

hardware support
server

The JSON parser/handler brings in dependencies to the core library that I'd like to avoid. We should externalize parsers and make them part of setup. Note that Protobufs could still...

IPC tests just sit there forever on mac/linux. We should add a timeout and also figure out what's wrong exactly.

Got tests running on azure on all platforms, just to find out that Message transmission mode is a windows kernel feature that doesn't exist for pipes in *nix land. Oops.

bug
library

Since commands like VibrateCmd take a float from 0-1, we can get very small numbers. However, sex toys have 100 steps of settings if we're lucky, with that number going...

hardware support
testing

Right now the Magic Motion protocol handler uses a switch block and name based identification to switch protocols. We should split these into separate classes that can be added to...

hardware support

CueMe has 8 vibrators. We should provide some sort of index for them in comments, with links to STPIHKAL.

hardware support