blackspherefollower

Results 102 issues of blackspherefollower

Building using: `./Configure no-shared no-gost darwin64-arm64-cc -g -fPIC -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX11.1.sdk -mmacosx-version-min=11.1` fails with: ``` clang -Iinclude -arch arm64 -O3 -Wall -g -fPIC -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX11.1.sdk -mmacosx-version-min=11.1 -D_REENTRANT -DNDEBUG -MMD -MF test/v3ext.d.tmp -MT test/v3ext.o...

branch: 1.1.1
triaged: bug

This fixes #664 by switching the dictionary implementaion used for _devices to ConcurrentDictionary.

Unfortunately I lost the log, but whilst testing the Xamarin examples I hit an issue where _devices is modified during access, resulting in an exception. I believe multiple Vibratissimo devices...

All known devices (except the JoyCon) have been expanded as per the new configuration atrributes scheme. This change adds FeatureOrder to the GenericMessageAttributes block and allows rxpressure as an endpoint...

The `ButtplugWebsocketConnector(Uri aUri)` constructor is missing the documented parameter `boolean aIgnoreSSLErrors`. This is required to connect to SSL Webscocket based servers which use self-signed certs.

Building OpenSSL 3.0.7 with either 32-bit or 64-bit mingw64 4.7.2 results in: ``` gcc -I. -Iinclude -Iproviders/common/include -Iproviders/implementations/include -DAES_ASM -DBSAES_ASM -DCMLL_ASM -DECP_NISTZ256_ASM -DGHASH_ASM -DKECCAK1600_ASM -DMD5_ASM -DOPENSSL_BN_ASM_GF2m -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_CPUID_OBJ -DOPENSSL_IA32_SSE2...

issue: bug report

``` node_modules/buttplug/dist/main/src/server/managers/forwardeddevices/ForwardedDeviceProtocol.d.ts(18,5): error TS2416: Property 'ParseMessage' in type 'ForwardedDeviceProtocol' is not assignable to the same property in base type 'ButtplugDeviceProtocol'. Type '(aMsg: ButtplugDeviceMessage) => Promise' is not assignable to type...

This PR includes support for the Flexer (patched and unpatched) and Gravity for both Lovense Connect and BLE. Also includes a fix for #506 to address the multi-vibe support on...

**Describe the bug** Testing the Gravity with both dongles, `Vibrate1:N;` followed quickly with `Vibrate2:N;` only causes the vibrator to be changed. Both messages are sent to the dongle (as far...

**Describe the bug** When you send a VibrateCmd with only a single index specified, the protocol logic sees only 1 vibrator value to update, but mistakes this for a single...

bug