Derive for several enums
This commit is contained in:
12
CHANGELOG.md
12
CHANGELOG.md
@@ -6,20 +6,24 @@ file. This change log follows the conventions of
|
||||
|
||||
## [Unreleased]
|
||||
|
||||
### Added
|
||||
|
||||
- `Condition`, `DataType`, `FacilityType` and `Period` now derive `Debug`.
|
||||
|
||||
### Fixed
|
||||
|
||||
- Docs.rs build should now pass. Take #2.
|
||||
|
||||
## [v0.1.1] - 2022-10-23
|
||||
|
||||
### Fixed
|
||||
|
||||
- Docs.rs build should now pass.
|
||||
|
||||
### Changed
|
||||
|
||||
- The docs and README files have been improved.
|
||||
|
||||
### Fixed
|
||||
|
||||
- Docs.rs build should now pass.
|
||||
|
||||
## [v0.1.0] - 2022-10-22
|
||||
|
||||
### Initial Release of simconnect-sdk
|
||||
|
@@ -1,7 +1,7 @@
|
||||
use crate::bindings;
|
||||
|
||||
/// Specifies under which conditions the data is to be sent by the server and received by the client.
|
||||
#[derive(Debug)]
|
||||
#[derive(Debug, Clone)]
|
||||
pub enum Condition {
|
||||
/// The default, data will be sent strictly according to the defined period.
|
||||
None,
|
||||
|
@@ -1,5 +1,5 @@
|
||||
/// [`crate::SimConnectObject`] object property data type.
|
||||
#[derive(Debug)]
|
||||
#[derive(Debug, Clone)]
|
||||
pub enum DataType {
|
||||
Float64,
|
||||
Bool,
|
||||
|
@@ -2,7 +2,7 @@ use crate::bindings;
|
||||
|
||||
/// Facility Type. The simulation keeps a facilities cache of all the airports, waypoints, NDB and VOR stations within a certain radius of the user aircraft.
|
||||
/// They can be requested using [`crate::SimConnect::subscribe_to_facilities`] or [`crate::SimConnect::request_facilities_list`].
|
||||
#[derive(Debug)]
|
||||
#[derive(Debug, Clone)]
|
||||
pub enum FacilityType {
|
||||
Airport,
|
||||
Waypoint,
|
||||
|
@@ -5,7 +5,7 @@ use crate::bindings;
|
||||
/// 1 - every other interval.
|
||||
/// 2 - every third interval.
|
||||
/// etc.
|
||||
#[derive(Debug)]
|
||||
#[derive(Debug, Clone)]
|
||||
pub enum Period {
|
||||
/// Specifies that the data should be sent once only. Note that this is not an efficient way of receiving data frequently, use one of the other periods if there is a regular frequency to the data request.
|
||||
Once,
|
||||
|
Reference in New Issue
Block a user