-
Notifications
You must be signed in to change notification settings - Fork 657
mavgen_objc.py: rename BOOL to MAV_BOOL #1098
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
mavgen_objc.py: rename BOOL to MAV_BOOL #1098
Conversation
I would prefer MAV_BOOL |
generator/mavgen_objc.py
Outdated
@@ -45,7 +45,7 @@ def generate_mavlink(directory, xml): | |||
@param mavlink The MVMavlink object calling this method | |||
@param data NSData object containing the bytes to be sent | |||
*/ | |||
- (BOOL)mavlink:(MVMavlink *)mavlink shouldWriteData:(NSData *)data; | |||
- (MAV_OPTION)mavlink:(MVMavlink *)mavlink shouldWriteData:(NSData *)data; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- (MAV_OPTION)mavlink:(MVMavlink *)mavlink shouldWriteData:(NSData *)data; | |
- (MAV_BOOL)mavlink:(MVMavlink *)mavlink shouldWriteData:(NSData *)data; |
generator/mavgen_objc.py
Outdated
@@ -70,7 +70,7 @@ def generate_mavlink(directory, xml): | |||
@param message Object conforming to the MVMessage protocol that represents the data to be sent | |||
@return YES if message sending was successful | |||
*/ | |||
- (BOOL)sendMessage:(id<MVMessage>)message; | |||
- (MAV_OPTION)sendMessage:(id<MVMessage>)message; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- (MAV_OPTION)sendMessage:(id<MVMessage>)message; | |
- (MAV_BOOL)sendMessage:(id<MVMessage>)message; |
generator/mavgen_objc.py
Outdated
@@ -103,7 +103,7 @@ def generate_mavlink(directory, xml): | |||
} | |||
} | |||
|
|||
- (BOOL)sendMessage:(id<MVMessage>)message { | |||
- (MAV_OPTION)sendMessage:(id<MVMessage>)message { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- (MAV_OPTION)sendMessage:(id<MVMessage>)message { | |
- (MAV_BOOL)sendMessage:(id<MVMessage>)message { |
7624af9
to
9887623
Compare
Renamed MAV_OPTION to MAV_BOOL |
@peterbarker Thanks, but can you merge it too - or give me rights to merge things that are already approved. |
@@ -45,7 +45,7 @@ def generate_mavlink(directory, xml): | |||
@param mavlink The MVMavlink object calling this method | |||
@param data NSData object containing the bytes to be sent | |||
*/ | |||
- (BOOL)mavlink:(MVMavlink *)mavlink shouldWriteData:(NSData *)data; | |||
- (MAV_BOOL)mavlink:(MVMavlink *)mavlink shouldWriteData:(NSData *)data; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So this this already support the BOOL enum we added? My assumption is that it did and this is why you need to change it? That was a quick addition.
Part of mavlink/mavlink#2317 initiative.