2.5.3: More Maintenance

This is another maintenance update that handles breaking library changes for:

• buttplug 7.1.16 -> 8.0.0 (changelog). Notably this adds new device support.
• iced 0.10 -> 0.12 (changelog). This should have no user-facing changes.

2.5.2: Maintenance Release

This release only updates dependencies, notably going from buttplug 7.1.15 to 7.1.16. This fixes a few issues you can read about in the buttplug changelog.

2.5.1: Maintenance Release

Hello, it's been 3 months since the last maintenance release, so here's another one.

• update dependencies, including patching for two vulnerabilities. Note that while it's unlikely we're impacted by either vulnerability, I still recommend updating just in case.
  • RUSTSEC-2023-0074
  • RUSTSEC-2024-0003

2.5.0: Maintenance Release

No major changes this time. Just a few maintenance chores:

• Upgrade many internal dependencies (most notably gui, http, bluetooth, and sex device libraries). That's 7 months of bugfixes and improvements.
• Include git commit hash in version information. This makes it possible to distinguish between different prerelease versions compiled with the same version number.
• Add --no-panic-handler and --force-panic-handler arguments for finer control over when the panic handler is enabled. These are for debugging and you can ignore them.

2.4.1: Logging has been broken for a month and nobody noticed

Hello again, it's been about a month since the last release. This time around is just a small bugfix & maintenance update.

• Fixes a bug that prevented log file contents from being written to disk
• Updates a bunch of dependencies
  • make github stop complaining about some vulnerability drama (buttplug-lite wasn't actually affected).
  • updates the GUI dependency, iced, to 0.9. The iced devs really like breaking changes, so it's a bit of a pain every time they do a new release.

2.4.0: Duplicate Device Support

User-facing changes

• Adds duplicate device support, finally resolving #3. Now if you have two different Edges in who-knows-what-holes you can drive them properly.
  • Your existing configurations will still work and will appear with a "[LEGACY]" tag in the UI. If you drive these tags, then all devices of the same type will react.
  • To clear the "[LEGACY]" devices, simply move your tags over to the new non-legacy device and save.
• The GUI now opens slightly faster, as it is no longer blocked by the HTTP call used to check for new versions
• Application crash reports are now logged to the log file. Previously, they went nowhere.
• We've got mac M1 binaries now... just in case anyone wanted that?

Internal changes

• Finished work on project reorganization. main.rs is now a sane length, weighing in at ~130 lines.

2.3.0: The unfuckening of the UI

User-facing changes

• Invalid motor tags are now highlighted red, and prevent saving. This includes duplicate tags, or tags containing a : or ;. You couldn't actually save invalid tags before, but if you tried it'd put the UI in a weird state.
• Mitigate a bug where any pending changes to a motor tag field would be cleared periodically. The bug still technically exists, but it should be exceptionally rare now. If you'd like to experience the bug, use the --debug-ticks 1 command-line argument. You'll hate it.
• The update button is now scary and red, because I really want people to see it. Here I am slaving away in the code mines so you dang users had better appreciate my updates 😡.

Internal changes

• Massive refactoring of the code to be much better organized. main.rs is still ~800 lines though, so there's more work to do.
• The beginning of duplicate device support (#3) is now in place, but for now it's only logged and nothing is actually done with it.
• I already had some alerting in place for vulnerable dependencies, but now I have more alerting. I've dropped my dependency on the time crate as a result of this, as apparently it's able to segfault.

This update may not look like much, but ~13 hours of work went into it. There was a lot of research put in to figuring out the least bad way of doing things.

2.2.0: The Logging Update

buttplug-lite now logs to to proper log files, and the awful console window is now gone. The location of these new files is documented in the readme. If for some reason you need buttplug-lite to log to stdout, there are command line arguments to do this which are also documented in the readme.

2.1.0: More device support

• Updates the underlying GUI library, iced, from v0.4.2 to v0.8.0. Due to changes in how iced handles theming the appearance of buttplug-lite is slightly different now, as the old look is not 100% reproducible in the new system (at least not without doing a ludicrous amount of work).
• Updates buttplug from v6.3.0 to v7.0.2. This introduces a new "unknown" ActuatorType which may appear in your configuration files (potentially breaking configuration loading if you downgrade back to buttplug-lite 2.0.x). A number of new devices have also been added which you can read more about in the buttplug changelog.

2.0.2: Spooky Vulnerabilty

Updates dependencies, one of which had a vulnerability allowing path traversal on Windows builds.