mirror of https://github.com/ArduPilot/ardupilot
541cfa022b
The squares surrounding the current location were only checked when we went to send a terrain request. This means it was possible that: - the number of pending requests could go to zero - prearm checks would pass - vehicle arm is attempted by the user (or a script, or ....) - the code would call AP_Terrain::send_requests which would create more pending requests - the arming sequence would fail It's also possible for the arming to succeed, and then we're flying in violation of the intended prearm checks. Doing things in the update function has the additional advantage of making things more efficient as we can push out terrain requests more often. |
||
|---|---|---|
| .. | ||
| tools | ||
| AP_Terrain.cpp | ||
| AP_Terrain.h | ||
| TerrainGCS.cpp | ||
| TerrainIO.cpp | ||
| TerrainMission.cpp | ||
| TerrainUtil.cpp | ||