On Mon, May 24, 2010 at 5:35 AM, Torsten Dreyer wrote: > Hi, > > triggered by an idea of James aka zakalawe, the xml autopilot has now the > ability to implement flip flops. They provide a method to add a state to > the > logic of an autopilot and probably may remove the need for many lines of > supporting nasal code > . >
Hi Torsten, Here's a dumb question. Many of these flip-flop variants require a clock. What is expected to serve as a clock signal in our system? Would this typically be the output of another filter or flip flop? It doesn't make sense in this context to imagine an actual time value. :-) And I don't think we provide a clock "signal" that rises and falls at some particular rate. This all sounds really low level, but I suppose there is no harm in adding it if the "if/then/else" structure parsing the section tags doesn't become to unwieldy. Thanks, Curt. -- Curtis Olson: http://baron.flightgear.org/~curt/
------------------------------------------------------------------------------
_______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
