<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.0.4630.0">
<TITLE>Implementing Escape Behaviors</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<P><FONT COLOR="#000080" SIZE=2 FACE="Comic Sans MS">As I mentioned, I have the Create working with behaviors. Tonight I identified a third "escape" behavior. The three escapes are "bump", "trapped", and "undock". All do the same thing with slightly different parameters: back, spin, and drive.</FONT></P>
<P><FONT COLOR="#000080" SIZE=2 FACE="Comic Sans MS">I can implement the action as a function called by each of the behaviors. I already have that for bump and trapped. </FONT>
</P>
<P><FONT COLOR="#000080" SIZE=2 FACE="Comic Sans MS">But I am wondering if "escape" should be a behavior of its own triggered by virtual sensor, say, "flight" that is set by the three escape behaviors. Flight could have different values. Bump would set it to "go around" while trapped and undock are "run away". Maybe there are other escapes behaviors that could be setup? Yup, just thought of one. When I get the IR proximity detectors setup they will require a milder version of "go around" than implemented with bump. </FONT></P>
<P><FONT COLOR="#000080" SIZE=2 FACE="Comic Sans MS">I keep thinking of "fight or flight" responses. Fundamental question is when do behaviors drive other behaviors versus reusing hard-coding actions. </FONT></P>
<P><FONT FACE="Times New Roman"> </FONT>
<BR><B><FONT COLOR="#000080" FACE="Comic Sans MS">Rud Merriam K5RUD</FONT><FONT FACE="Times New Roman"></FONT></B><BR>
<FONT COLOR="#000080" FACE="Comic Sans MS">ARES AEC Montgomery County, TX</FONT>
<BR><I></I><A HREF="http://TheHamNetwork.net"><I><U></U></I><I><U><FONT COLOR="#0000FF" FACE="Comic Sans MS">http://TheHamNetwork.net</FONT></U></I><I></I></A><I></I>
</P>
</BODY>
</HTML>