Ignore:
Timestamp:
07/21/12 12:43:34 (12 years ago)
Author:
István Váradi <ivaradi@…>
Branch:
default
hg-Phase:
(<MercurialRepository 1 'hg:/home/ivaradi/mlx/hg' '/'>, 'public')
Message:

Documented the non-GUI modules

File:
1 edited

Legend:

Unmodified
Added
Removed
  • src/mlx/fsuipc.py

    r290 r298  
    1 # Module handling the connection to FSUIPC
    2 
    3 #------------------------------------------------------------------------------
    41
    52import fs
     
    2219#------------------------------------------------------------------------------
    2320
    24 # The mapping of tank types to FSUIPC offsets
     21## @package mlx.fsuipc
     22#
     23# The module towards FSUIPC.
     24#
     25# This module implements the simulator interface to FSUIPC.
     26#
     27# The \ref Handler class is thread handling the FSUIPC requests. It can be
     28# given read, periodic read and write, requests, that are executed
     29# asynchronously, and a callback function is called with the result. This class
     30# is used internally within the module.
     31#
     32# The \ref Simulator class is the actual interface to the flight simulator, and
     33# an instance of it is returned by \ref mlx.fs.createSimulator. This object can
     34# be used to connect to the simulator and disconnect from it, to query various
     35# data and to start and stop the monitoring of the data.
     36#
     37# \ref AircraftModel is the base class of the aircraft models. A "model" is a
     38# particular implementation of an aircraft, such as the PMDG Boeing 737NG in
     39# Flight Simulator 2004. Since each type and each model has its peculiarities
     40# (e.g. the different engine and fuel tank configurations), each aircraft type
     41# has a generic model, that should work for most of the time. However, certain
     42# models may implement various controls, gauges, etc. differently, and such
     43# peculiarites can be handled in a specific subclass of \ref
     44# AircraftModel. These subclasses should be registered as special ones, and if
     45# the simulator detects that the aircraft's model became known or has changed,
     46# it will check these special models before resorting to the generic ones.
     47#
     48# The models are responsible also for querying certain parameters, such as the
     49# fuel tank configuration. While ideally it should be specific to a type only,
     50# it is possible that the model contains different tanks, in which case some
     51# tricks may be needed. See the \ref DC3Model "DC-3 (Li-2)" aircraft as an
     52# example.
     53
     54#------------------------------------------------------------------------------
     55
     56## The mapping of tank types to FSUIPC offsets
    2557_tank2offset = { const.FUELTANK_CENTRE : 0x0b74,
    2658                 const.FUELTANK_LEFT : 0x0b7c,
Note: See TracChangeset for help on using the changeset viewer.