Fix a bug where ATTITUDE messages were not causing the attitude display to update

I posted about this being broken for the AR Drone on the google+ group.  Turns out the issue was a simple bug caused by confusion between the ATTITUDE and ORIENTATION events.
The attitude display was not updating until an (unrelated) ORIENTATION event was received:
Correct spelling of ATTITUDE event.
Correct  misuse of ORIENTATION event where ATTITUDE was needed.
Should this method be renamed?