Deferring using a 0mS timer does not work for Fox logging as it may be
invoked more than once in a loop when multiple streams are
active. This change directly calls the logging member function(s)
inside the message processing loop.
This change was initially made because an unhelpful database query
order along with a need to display the latest logged QSO at the bottom
of the Fox log table view was causing GUI unresponsiveness when the
Fox log table had many rows. The current implementation shows the Fox
log table view in descending time order with the latest logged QSO at
the top which avoids this unresponsiveness issue (tested with a Fox
log table with over 15,000 rows).
fd7bca080a