v1.2.1
SlimeTora v1.2.1 - here, let me do it for you!
The first bugfix release for SlimeTora is now out! This is a hotfix that fixes COM ports not being detected by the program if on Windows and handle more types of errors with new error messages.
Changelogs
- Fix COM ports not showing up for Windows users due to incorrect filtering
- uhhh.. my bad lol. me when i break slimetora for windows users only (aka 99.99% of people). time to switch to linux guys!
- Thank you to
the_flyingangel
on Discord for reporting it so quickly!
- Handle more errors with new error messages
- Error message when failing to write data to trackers (e.g. heartbeat, tracker settings)
- Error message when an unexpected error happens
Known issues
- Battery information jumps to incorrect percentages/voltage randomly
- Unfortunately this is an issue I can't fix.. because it's literally an issue with the trackers themselves
- This has been slightly mitigated with v1.2.0, which uses a "stable average" of the battery percentage and voltage instead
- Running "auto-detection" more than once without restarting breaks tracker settings auto-detection (device/ports detection still works)
- (LINUX) Connecting to trackers via "Bluetooth (LE)" always fails
- The Bluetooth package we are using, noble, requires root/sudo to be able to interact with BLE devices - its workarounds (and running as sudo) break Electron due to
setcap
disabling theLD_LIBRARY_PATH
environment variable for security and modifying thebluetooth.conf
for dbus does not work (at least, for me) - Any help on this is appreciated, though haritorax-interpreter may need to use both noble and node-ble (with a minor tweak on the user's side) to work.
- The Bluetooth package we are using, noble, requires root/sudo to be able to interact with BLE devices - its workarounds (and running as sudo) break Electron due to
- Starting a connection via Bluetooth may show a "connection failed" error, even though trackers are working fine
Full Changelog: 1.2.0...v1.2.1