Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / buttplugio/buttplug-rs-ffi issues and pull requests
#100 - The current (1.5 year old) binaries don't work on current versions of ubuntu. (wants libssl1.1, is provided libssl3)
Issue -
State: open - Opened by kitlith almost 2 years ago
- 1 comment
Labels: bug
#99 - Move exception catch for missing natives
Pull Request -
State: open - Opened by kitlith almost 2 years ago
- 3 comments
#98 - FFI should allow for arbitrary connectors
Issue -
State: open - Opened by kitlith almost 2 years ago
#97 - Java fails to build
Issue -
State: open - Opened by catqwe almost 2 years ago
Labels: bug
#96 - Update getrandom for NW.js compatibility
Pull Request -
State: open - Opened by qazmlp about 2 years ago
- 1 comment
#95 - Runtime error regarding undefined imports on Buttplug versions 1.0.15 - 1.0.17 when using Webpack 5
Issue -
State: open - Opened by amydevs about 2 years ago
Labels: bug
#94 - build (js): Update Webpack to Webpack 5
Pull Request -
State: open - Opened by squishyfoxkitten over 2 years ago
- 1 comment
#93 - Build Error on latest version - Module not found: Error: Can't resolve '#buttplug_rs_ffi_bg'
Issue -
State: open - Opened by myhubiuser1 over 2 years ago
- 2 comments
Labels: bug
#92 - Add README to the js build to explain how to build.
Issue -
State: open - Opened by phckr about 3 years ago
- 1 comment
#91 - JS: Load WASM from a specified path
Issue -
State: open - Opened by blackspherefollower about 3 years ago
#90 - fix: Revert "js: Add url to wasm file as argument to buttplugInit"
Pull Request -
State: closed - Opened by blackspherefollower about 3 years ago
#89 - The scanningfinished event is emitted at the wrong time (as far as I can tell).
Issue -
State: open - Opened by phckr about 3 years ago
- 3 comments
Labels: bug
#88 - JS/WASM 1.0.15 loading broken
Issue -
State: closed - Opened by blackspherefollower about 3 years ago
Labels: bug
#87 - C# can emit null devices when connecting to a server with multiple devices already attached.
Issue -
State: closed - Opened by qdot over 3 years ago
Labels: bug
#86 - js: Add url to wasm file as argument to buttplugInit
Pull Request -
State: closed - Opened by kitlith over 3 years ago
#85 - Buttplug incorrectly states Chrome for Andoird doesn't support the WebBluetooth API
Issue -
State: closed - Opened by DXsmiley over 3 years ago
- 2 comments
Labels: bug
#84 - Add buttplug_rs_ffi.dll.lib file to windows releases
Issue -
State: closed - Opened by sa-wilson over 3 years ago
- 1 comment
Labels: Core FFI, build
#83 - Add node native bindings and prebuild
Pull Request -
State: open - Opened by itsame-luigi over 3 years ago
- 4 comments
#82 - Add README with build information to the Java FFI
Issue -
State: open - Opened by qdot over 3 years ago
- 1 comment
Labels: Java
#81 - JS ButtplugClientDevice equality testing doesn't work
Issue -
State: closed - Opened by qdot over 3 years ago
- 1 comment
Labels: bug, WASM
#80 - Add support for NodeJS using ESM
Pull Request -
State: closed - Opened by itsame-luigi over 3 years ago
- 3 comments
#79 - C# dispose methods should handle re-entrancy
Issue -
State: closed - Opened by qdot over 3 years ago
Labels: bug
#78 - C# throws duplicate key error when second client created
Issue -
State: closed - Opened by qdot over 3 years ago
Labels: bug, C#
#77 - C# code cleanup
Pull Request -
State: closed - Opened by Yoooi0 over 3 years ago
- 1 comment
#76 - SEHException when a device is connected or disconnected
Issue -
State: closed - Opened by Yoooi0 over 3 years ago
- 4 comments
Labels: bug
#75 - Convert public fields to public properties in C# classes
Issue -
State: closed - Opened by Yoooi0 over 3 years ago
- 1 comment
#74 - Replace protobufs with cbindgen headers
Issue -
State: open - Opened by qdot over 3 years ago
Labels: Core FFI
#73 - Line up WASM and native exported calls
Issue -
State: open - Opened by qdot over 3 years ago
#72 - Remove message sorter from WASM
Issue -
State: open - Opened by qdot over 3 years ago
#71 - Remove message sorter from C#
Issue -
State: open - Opened by qdot over 3 years ago
Labels: C#
#70 - Non protobuf API
Pull Request -
State: closed - Opened by kitlith over 3 years ago
- 2 comments
#69 - Make C# message sorter future failures throw specific type exceptions
Issue -
State: closed - Opened by qdot over 3 years ago
Labels: bug, C#
#68 - Separate protobuf messages from buttplug to consumer into system messages and return values for client/device "method" calls
Issue -
State: open - Opened by kitlith over 3 years ago
- 2 comments
#67 - Rename functions that deal with protobuf
Pull Request -
State: closed - Opened by kitlith over 3 years ago
- 2 comments
#66 - Bundle callback method and context pointer for easier passing/execution
Issue -
State: open - Opened by qdot over 3 years ago
Labels: Core FFI
#65 - Try tying logging lifetime to client instances
Issue -
State: closed - Opened by qdot over 3 years ago
- 1 comment
Labels: Core FFI
#64 - Rename currently exposed methods to denote protobuf requirements
Issue -
State: closed - Opened by qdot over 3 years ago
Labels: Core FFI
#63 - Java FFI
Pull Request -
State: closed - Opened by kitlith over 3 years ago
- 5 comments
#62 - Calling response methods on a disconnected client device can disable all device comms
Issue -
State: closed - Opened by qdot over 3 years ago
- 2 comments
Labels: bug, C#
#61 - C# Client Sorter Callback crash
Issue -
State: closed - Opened by sippeangelo over 3 years ago
Labels: bug
#60 - Buttplug.Endpoint not exported to JS?
Issue -
State: closed - Opened by WesleyAC over 3 years ago
- 2 comments
Labels: bug
#59 - js: ButtplugClientDevice.vibrate does not take an array of numbers
Issue -
State: closed - Opened by WesleyAC almost 4 years ago
- 2 comments
Labels: bug
#58 - C# Client Sorter Callback should be run context of the .Net Scheduler
Issue -
State: closed - Opened by qdot almost 4 years ago
Labels: bug
#57 - CDN Loading can break when script tags use defer
Issue -
State: open - Opened by qdot almost 4 years ago
Labels: bug, WASM
#56 - Reconnecting to a server with already connected devices can cause repeated DeviceAdded calls
Issue -
State: closed - Opened by qdot almost 4 years ago
- 1 comment
Labels: bug, Core FFI, C#
#55 - Change nav.bluetooth() WASM check to handling optional loading
Issue -
State: closed - Opened by qdot almost 4 years ago
Labels: WASM
#54 - Respond to BluetoothDevice gattserverdisconnected event
Pull Request -
State: closed - Opened by CirrusNeptune almost 4 years ago
- 1 comment
#53 - Add .Net Framework build for C#
Issue -
State: closed - Opened by qdot almost 4 years ago
- 1 comment
#52 - WebBluetooth: client.AllowedMessages has the wrong datatype
Issue -
State: closed - Opened by ftreesmilo almost 4 years ago
- 1 comment
Labels: bug
#51 - WebBluetooth: client.isScanning is still true after user selects device
Issue -
State: closed - Opened by ftreesmilo almost 4 years ago
Labels: bug
#50 - WebBluetooth writes panic on failure
Issue -
State: open - Opened by qdot almost 4 years ago
- 1 comment
Labels: bug, Core FFI, WASM
#49 - JS LinearCmd runs RotateCmd checks
Issue -
State: closed - Opened by qdot almost 4 years ago
Labels: bug, WASM
#48 - Discord invite in readme has expired
Issue -
State: closed - Opened by ftreesmilo almost 4 years ago
- 1 comment
Labels: bug
#47 - SendVibrateCmd only vibrates one motor
Issue -
State: closed - Opened by sippeangelo almost 4 years ago
#46 - [C#] Add null checking for events on invoke
Pull Request -
State: closed - Opened by tjhorner almost 4 years ago
- 5 comments
#45 - Unhandled exception. System.ArgumentException: An item with the same key has already been added.
Issue -
State: closed - Opened by kyrahabattoir almost 4 years ago
Labels: bug
#44 - C# StartLogHandler() crashes due to native held reference
Issue -
State: closed - Opened by qdot almost 4 years ago
- 1 comment
Labels: bug, C#
#43 - protobufjs dependency missing from WASM package
Issue -
State: closed - Opened by qdot almost 4 years ago
- 1 comment
Labels: bug, WASM
#42 - WebBluetooth scanning doesn't throw when triggered without user gesture
Issue -
State: open - Opened by qdot almost 4 years ago
- 1 comment
Labels: bug, WASM
#41 - doc: fix link to npm for the WASM/TypeScript/JavaScript implementation
Pull Request -
State: closed - Opened by petetnt almost 4 years ago
- 2 comments
#40 - Add support for more platforms in the produced FFI binaries
Issue -
State: open - Opened by qdot almost 4 years ago
- 2 comments
Labels: C#
#39 - WASM Websockets should bubble JS exception back to top
Issue -
State: open - Opened by qdot almost 4 years ago
Labels: bug, WASM
#38 - WASM Websockets don't handle invalid opens correctly
Issue -
State: closed - Opened by qdot almost 4 years ago
- 1 comment
Labels: bug, WASM
#37 - Add a read-only property to ButtplugClient that indicates whether scanning is in progress.
Issue -
State: closed - Opened by kyrahabattoir almost 4 years ago
#36 - Add a "Connected" read-only property to ButtplugClient
Issue -
State: closed - Opened by kyrahabattoir almost 4 years ago
#35 - c# ButtplugClient events not firing.
Issue -
State: closed - Opened by kyrahabattoir almost 4 years ago
- 3 comments
Labels: bug, C#
#34 - Implement error types in WASM
Issue -
State: closed - Opened by qdot almost 4 years ago
Labels: WASM
#32 - Expose test devices to FFI
Issue -
State: open - Opened by qdot about 4 years ago
Labels: enhancement, Core FFI
#31 - Guidance building an example JS app
Issue -
State: closed - Opened by highfiiv about 4 years ago
- 2 comments
#30 - WASM is built w/ async/multithreading strategies that may not be needed.
Issue -
State: closed - Opened by qdot about 4 years ago
- 1 comment
Labels: bug, question, WASM
#29 - futures_timer methods in buttplug-rs will panic WASM FFI
Issue -
State: closed - Opened by qdot about 4 years ago
- 1 comment
Labels: bug, WASM
#28 - WASM clients can't set up event handlers before connection
Issue -
State: closed - Opened by qdot about 4 years ago
- 1 comment
Labels: bug, WASM
#27 - Add device index getter for ButtplugClientDevice WASM
Issue -
State: closed - Opened by qdot about 4 years ago
- 1 comment
Labels: WASM
#26 - Add connected status getter to WASM ButtplugClient
Issue -
State: closed - Opened by qdot about 4 years ago
- 1 comment
Labels: WASM
#25 - Add removeListener method for WASM event managers
Issue -
State: closed - Opened by qdot about 4 years ago
- 1 comment
Labels: WASM
#24 - Turn log messages into pbufs before they leave rust ffi
Issue -
State: open - Opened by qdot about 4 years ago
Labels: enhancement, Core FFI
#23 - Add log level resetting for FFI libraries
Issue -
State: open - Opened by qdot about 4 years ago
- 1 comment
Labels: enhancement, Core FFI, C#, WASM
#22 - Implement test executable for FFI completeness
Issue -
State: open - Opened by qdot about 4 years ago
Labels: testing
#21 - Implement address passing for websockets in c#
Issue -
State: closed - Opened by qdot about 4 years ago
- 1 comment
Labels: C#
#20 - Figure out method for Python PyPi package redistribution
Issue -
State: open - Opened by qdot about 4 years ago
Labels: Python, build
#19 - Figure out how to include native rust library in C# nuget distribution
Issue -
State: closed - Opened by qdot about 4 years ago
- 1 comment
Labels: C#, build
#18 - Figure out how documentation will work for each implementation
Issue -
State: open - Opened by qdot about 4 years ago
Labels: documentation, question, Core FFI, C#, Python, C, WASM, Java, Node
#17 - Implement RSSI Message in all implementations
Issue -
State: closed - Opened by qdot about 4 years ago
- 1 comment
Labels: C#, WASM
#16 - Implement Battery message in C# Client Device
Issue -
State: closed - Opened by qdot about 4 years ago
- 1 comment
Labels: duplicate, C#
#15 - Implement Battery message
Issue -
State: closed - Opened by qdot about 4 years ago
- 1 comment
Labels: Core FFI, C#, WASM
#14 - Implement Disconnect method in Client
Issue -
State: closed - Opened by qdot about 4 years ago
Labels: Core FFI, C#, WASM
#13 - Implement Raw Messages
Issue -
State: closed - Opened by qdot about 4 years ago
- 2 comments
Labels: Core FFI, C#, WASM
#12 - Implement Message Attributes for FFI
Issue -
State: closed - Opened by qdot about 4 years ago
- 1 comment
Labels: Core FFI, C#, WASM
#11 - How should we support WASM/Neon on NPM?
Issue -
State: closed - Opened by qdot about 4 years ago
- 2 comments
Labels: question, WASM, Node, build
#10 - Add bluetooth detection output to wasm glitch tutorials
Issue -
State: open - Opened by qdot about 6 years ago
Labels: WASM
#9 - Consider making a React Native device manager
Issue -
State: open - Opened by qdot about 6 years ago
- 1 comment
Labels: WASM
#8 - Add stop_all_devices to all FFI client APIs.
Issue -
State: closed - Opened by qdot about 4 years ago
- 1 comment
Labels: enhancement, Core FFI, C#, Python, WASM, Java
#7 - Freeze lock files
Issue -
State: closed - Opened by qdot about 4 years ago
- 1 comment
Labels: Core FFI
#6 - Add method for changing device and user config files
Issue -
State: closed - Opened by qdot over 4 years ago
- 1 comment
Labels: enhancement, Core FFI
#5 - Implement missing events (Ping out, scanning finished, etc)
Issue -
State: closed - Opened by qdot over 4 years ago
- 1 comment
Labels: Core FFI
#4 - Allow building Client only FFI
Issue -
State: open - Opened by qdot over 4 years ago
Labels: enhancement, Core FFI
#3 - Implement selection of Comm Managers for in-process connector
Issue -
State: closed - Opened by qdot over 4 years ago
- 1 comment
Labels: enhancement, Core FFI
#2 - Implement websocket connections through Rust FFI
Issue -
State: closed - Opened by qdot over 4 years ago
- 1 comment
Labels: enhancement, Core FFI
#1 - Add tracing logging export callback
Issue -
State: closed - Opened by qdot over 4 years ago
- 3 comments
Labels: enhancement, Core FFI