Skip to content

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

andrewvoznytsa
Copy link

Part of mavlink/mavlink#2317 initiative.

@tridge
Copy link
Contributor

tridge commented Jul 22, 2025

I would prefer MAV_BOOL

@@ -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;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- (MAV_OPTION)mavlink:(MVMavlink *)mavlink shouldWriteData:(NSData *)data;
- (MAV_BOOL)mavlink:(MVMavlink *)mavlink shouldWriteData:(NSData *)data;

@@ -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;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- (MAV_OPTION)sendMessage:(id<MVMessage>)message;
- (MAV_BOOL)sendMessage:(id<MVMessage>)message;

@@ -103,7 +103,7 @@ def generate_mavlink(directory, xml):
}
}

- (BOOL)sendMessage:(id<MVMessage>)message {
- (MAV_OPTION)sendMessage:(id<MVMessage>)message {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- (MAV_OPTION)sendMessage:(id<MVMessage>)message {
- (MAV_BOOL)sendMessage:(id<MVMessage>)message {

@andrewvoznytsa andrewvoznytsa force-pushed the rename-bool-to-mav_option branch from 7624af9 to 9887623 Compare July 23, 2025 08:06
@andrewvoznytsa
Copy link
Author

Renamed MAV_OPTION to MAV_BOOL

@peterbarker peterbarker changed the title mavgen_objc.py: rename BOOL to MAV_OPTION mavgen_objc.py: rename BOOL to MAV_BOOL Jul 23, 2025
@hamishwillee
Copy link
Contributor

@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;
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants