This is the fall vexide update (0.4.0) changelog! This is only the changelog for the vexide crate. For more in-depth info and a project update, read our fall update blog post.
Changelog
Added
- Added support for the V5 GPS Sensor (#79)
- Added support for custom banner themes configurable through the
vexide::main
macro (#127)
Fixed
- Fixed an issue where the distance sensor relative_size returned a u32 when it can be negative. (#116)
- Fixed an issue preventing the
Screen::draw_buffer
function from working properly. (#128) - Fixed an issue where panic messages would not be displayed even when the
display_panics
feature was enabled if the screens render mode was set toDoubleBuffered
. (#134) GpsImu
should now validate on the correct port. (#141)
Changed
- Refactored the distance sensor API. All readings from the sensor are now read at once in a
object
method that can be possiblyNone
if no object was detected. (#122) (Breaking Change) - Adjusted distance sensor status code errors to be more clear.
- Overhauled the design of the startup banner.
- Adjusted distance sensor error names. (#113) (Breaking Change)
- Renamed
SmartDevice::port_index
andSmartPort::index
toSmartDevice::port_number
andSmartPort::port_number
. (#121) (Breaking Change) - Renamed
AdiDevice::port_index
andAdiPort::index
toAdiDevice::port_number
andAdiDevice::port_number
. (#121) (Breaking Change) SmartPort::device_type
now no longer returns aResult
. (#121) (Breaking Change)- Updated the names of certain misspelled
enum
variants, constants, and fields. (#132) (Breaking Change) - Marks many futures as
#[must_use]
to warn when futures are created withoutawait
ing them. (#112) - Changes the banner attribute syntax in the
vexide::main
macro. (#127) (Breaking Change) - Controller joystick axis getters now return
f64
instead off32
. (#133) (Breaking Change) - Fixed an issue where the async executor would block indefinetly on the first program run after a Brain reboot (#139)
- Removed the
critical_section
module fromvexide_core
, since vexide doesn’t use interrupts and it can potentially break VEXos operations. (#144) (Breaking Change) - Switched to a hard-float libm build with up to 6 times faster floating point operations. (#145)