Changeset 71:354bda0cd5ac in xplra for doc/overview.dox


Ignore:
Timestamp:
04/13/13 13:05:40 (11 years ago)
Author:
István Váradi <ivaradi@…>
Branch:
default
hg-Phase:
(<MercurialRepository 3 'hg:/home/ivaradi/xplane/hg/xplra' '/'>, 'public')
Message:

Added the Python documentation

File:
1 edited

Legend:

Unmodified
Added
Removed
  • doc/overview.dox

    r70 r71  
    770770/*! \page pythonapi Python Client API
    771771 *
     772 * The Python client API is implemented as a single module. Its
     773 * central class is \ref xplra.XPlane. To communicate with the plugin
     774 * in X-Plane, create an instance of it and call its \ref
     775 * xplra.XPlane.connect "connect" function. This tries to establish
     776 * the connection, and throws the standard I/O exceptions if it fails.
     777 *
     778 * The class can be used to perform the various operations provided by
     779 * the plugin. In case of a failure and exception is thrown. If the
     780 * plugin signals an error, a \ref xplra.ProtocolException
     781 * "ProtocolException" is thrown with the error information provided
     782 * by the plugin. In other cases some standard exception is thrown,
     783 * which is mostly IOError if a communication error occurs.
     784 *
     785 * The \c XPlane object can be reused in the sense, that after you
     786 * have made a connection, you can disconnect and then connect
     787 * again. This may be useful, if X-Plane crashes for some reason, and
     788 * you can then reconnect if the user has restarted it.
     789 *
     790 * Objects to store information about multi-dataref queries can be
     791 * created by the \ref xplra.XPlane.createMultiGetter
     792 * "createMultiGetter" function. It returns an instance of \ref
     793 * xplra.MultiGetter, which can be used to store a number of datarefs
     794 * and then execute a multi-dataref query for those datarefs. Before
     795 * execution, the query can be \ref xplra.MultiBuffer.register
     796 * "registered" in the plugin, so that the client does not have to send
     797 * all the dataref information whenever the query is executed.
     798 *
     799 * The \c XPlane object knows about any multi-dataref query objects.
     800 * Therefore if you register such a multi-dataref query, and then the
     801 * connection breaks, and then you reconnect, the query will-be
     802 * re-registered too, i.e. you don't have to do it yourself.
     803 *
     804 * Similarly, the \ref xplra.XPlane.createMultiSetter
     805 * "createMultiSetter" function can be used to create a multi-dataref
     806 * update object. They are handled the same way by \c XPlane as the
     807 * query objects when it comes to registration and re-registration.
     808 *
     809 * The other functions of \c XPlane are mostly self-explanatory: they
     810 * perform the operations defined by the protocol.
    772811 */
Note: See TracChangeset for help on using the changeset viewer.