Releases: acmerobotics/ftc-dashboard
Releases · acmerobotics/ftc-dashboard
v0.4.16
v0.4.15
v0.4.14
Changes
- Add array config support by @MafteiAlbert-Alexandru in #144
- Link config variable labels to their inputs (fixes #118)
- Remove field flickering (fixes #141) and improves field framerate with default field drawing
- Add some icon tooltips (fixes #143)
- Show battery voltage in the top bar (fixes #129)
- Allow resizing of pause graphs without clearing (fixes #122)
Full Changelog: v0.4.13...v0.4.14
v0.4.13
v0.4.12
v0.4.11
Changes
- Move default drawing logic to the server with an option to disable, opening up easier custom fields.
- Field versatility improvements (#138, big thanks @IronReignRobotics)
- New drawing primitives (text, images, grids)
- Field coordinate system transformations (set origin, set rotation, set scaling)
- See the details on the [field view docs page[(https://acmerobotics.github.io/ftc-dashboard/fieldview).
v0.4.10
v0.4.9
Changes
A couple of stability improvements.
- Replace some throws with logs. The dash core refactor aggressively made some old catch clauses re-throw instead of log. Turns out that some of these were hit in the wild! In particular, there are edge cases around the socket lifecycle where dash may attempt to send messages on a socket that's already closed. The old behavior has been restored.
- The new
Mutex
container helps ensure access to certain variables is synchronized. It doesn't totally foreclose such bugs, but it makes them harder to write. (And this is as good an opportunity as any to remind everyone that the dashboard API is not thread-safe. Call it exclusively in op modes and you should be fine.)
0.4.8
0.4.7
Changes
- Display message in clients when disabled (addresses #104)
- Display null config variables (still no editing)
- Handle special floating point values (still no
- Stop leaking memory when disabled (fixes #100)
- Fix graph unpausing (fixes #98)
- Various changes under the hood (thanks @nash-pillai and especially @NoahBres)