MavLink Connection restructuring #1009
Conversation
Several core utilities not dependant on android were moved to 'Core'. The restructuring should also fix a persistently annoying 'save to log' bug, which i think might have been the result of a race condition.
…into fix_savetolog_bug Conflicts: Android/src/org/droidplanner/android/maps/providers/google_map/GoogleMapFragment.java
|
@arthurbenemann I'm heading out now to test the new changes in the field. I'll mostly focus on testing the Once i get back, i'll test |
|
@ne0fhyk I'll test the UDP and BT monday when I'm back at the office. I'm not sure if someone is still using TCP (2% according to analytics). |
|
@arthurbenemann No |
…into fix_savetolog_bug
…into fix_savetolog_bug Conflicts: Android/src/org/droidplanner/android/fragments/DroneMap.java
…into fix_savetolog_bug
…into fix_savetolog_bug
|
Looks good on Bt as well. I'm merging this for the next release. |
MavLink Connection restructuring
Rearchitecturing of the mavlink connection class structure:
Coreto allow reuse of logic in a platform agnostic way.Loggerinterface that allows logging in a platform agnostic way. Each platform must implement a provides its ownLoggerimplementation (i.e:org.droidplanner.android.utils.AndroidLoggeris the logger implementation for the Android platform).Connecting & Receiving, one thread forSending messages, and one thread forLogging. The threads communicates with each other, and the main thread using elements of the `java.util.concurrent' library.saveToLogbug.