curt 86249209b9 This is a work in progress. I am extending the "ExternalPipe" protocol to ... have a "property" mode as well as the original "binary" mode. The property mode will allow the remote module to request any set of properties, and it will send those properties each frame. The remote module can reply with a list of arbitrary property name/value pairs to update on the FlightGear side. This is a first stab, so it's not the cleanest, most well concieved code, but it allows an external module (communicating via a pipe) to have a huge amount of flexibility in the data in can access and update.		2005-04-19 01:44:56 +00:00
..
.cvsignore	Ignore generated files.	2003-03-09 03:21:34 +00:00
ExternalPipe.cxx	This is a work in progress. I am extending the "ExternalPipe" protocol to	2005-04-19 01:44:56 +00:00
ExternalPipe.hxx	This is a work in progress. I am extending the "ExternalPipe" protocol to	2005-04-19 01:44:56 +00:00
Makefile.am	First stab at a "named pipe" interface to an external FDM. Compared to the	2003-03-03 04:30:16 +00:00