In the logplayer, the data stream is read ahead for messages, which is used to determine the size of the output bytearrays. Previously, this wasn't done correctly resulting in non-ideal behavior. Now, the next message is scanned properly, so the only bytearrays that are emitted from QGCMAVLinkLogPlayer are MAVLink messages in their entirety. This also has the benefit of skipping invalid/corrupted messages in the log that's being played back.

Refactored QGC::groundTime*() functions to be simpler.

Master

Readme: dependencies for Arch Linux

Because the indexes into the stackedwidget are all wrong

There were two separate actions for the simulation view, leading to
strange behaviour when it was selected.

Set max zoom to wrong value for BING to avoid excessive memory consumption - this is a workaround, not a fix

Remove flightgear rate limitations

use correct severity level for waypoint reached event

Be more forgiving about component IDs, but warn developers. Do *not* translate developer debug messages (they would show up in the translation tool). Anyone without sufficient command of the english language will have a hard time contributing or debugging this application and we should not entangle the poor translators in this.

Build fixes

Clears the persisted settings for the QGC

This disables Windows C Runtime assert dialogs from popping up.