mirror of https://github.com/ArduPilot/ardupilot
AC_Fence: Fix some typos
Fixed some typos found in the code.
This commit is contained in:
parent
c5abee2f88
commit
567dedf3e3
|
@ -494,7 +494,7 @@ bool AC_Fence::check_fence_polygon()
|
|||
/// check_fence_circle - returns true if the circle fence (defined via
|
||||
/// parameters) has been freshly breached. May also set up a backup
|
||||
/// fence outside the fence and return a fresh breach if that backup
|
||||
/// fence is breaced.
|
||||
/// fence is breached.
|
||||
bool AC_Fence::check_fence_circle()
|
||||
{
|
||||
if (!(_enabled_fences & AC_FENCE_TYPE_CIRCLE)) {
|
||||
|
|
|
@ -6,7 +6,7 @@
|
|||
// CIRCLE_INCLUSION_INT stores the radius an a 32-bit integer in
|
||||
// metres. This was a bug, and CIRCLE_INCLUSION was created to store
|
||||
// as a 32-bit float instead. We save as _INT in the case that the
|
||||
// radius looks like an integer as a backwards-compatability measure.
|
||||
// radius looks like an integer as a backwards-compatibility measure.
|
||||
// For 4.2 we might consider only loading _INT and always saving as
|
||||
// float, and in 4.3 considering _INT invalid
|
||||
enum class AC_PolyFenceType {
|
||||
|
@ -352,7 +352,7 @@ private:
|
|||
|
||||
#if AC_POLYFENCE_FENCE_POINT_PROTOCOL_SUPPORT
|
||||
/*
|
||||
* FENCE_POINT protocol compatability
|
||||
* FENCE_POINT protocol compatibility
|
||||
*/
|
||||
void handle_msg_fetch_fence_point(GCS_MAVLINK &link, const mavlink_message_t& msg);
|
||||
void handle_msg_fence_point(GCS_MAVLINK &link, const mavlink_message_t& msg);
|
||||
|
@ -380,7 +380,7 @@ private:
|
|||
bool write_eos_to_storage(uint16_t &offset);
|
||||
|
||||
// _total - reference to FENCE_TOTAL parameter. This is used
|
||||
// solely for compatability with the FENCE_POINT protocol
|
||||
// solely for compatibility with the FENCE_POINT protocol
|
||||
AP_Int8 &_total;
|
||||
const AP_Int16 &_options;
|
||||
uint8_t _old_total;
|
||||
|
|
Loading…
Reference in New Issue