Home | History | Annotate | Download | only in util

Lines Matching defs:exit

36  * <code>processMessage</code> and optionally <code>enter/exit/getName</code>.
37 * The enter/exit methods are equivalent to the construction and destruction
76 * will exit the current state and its parent and then exit from the controlling thread
80 * an <code>enter</code> method and <code>exit</exit> method which may be overridden.</p>
85 * the current state is found. We then exit from the current state and its
121 * which is mP1. It will then call mS5.exit, mS1.exit, mS2.enter and then
166 exit { log("mP1.exit"); }
181 exit { log("mS1.exit"); }
193 exit { log("mS2.exit"); }
213 exit { log("mP2.exit"); }
280 &#64;Override public void exit() {
281 Log.d(TAG, "mP1.exit");
292 // Transition to ourself to show that enter/exit is called
300 &#64;Override public void exit() {
301 Log.d(TAG, "mS1.exit");
328 &#64;Override public void exit() {
329 Log.d(TAG, "mS2.exit");
351 &#64;Override public void exit() {
352 Log.d(TAG, "mP2.exit");
394 D/hsm1 ( 1999): mS1.exit
398 D/hsm1 ( 1999): mS1.exit
402 D/hsm1 ( 1999): mS2.exit
403 D/hsm1 ( 1999): mP1.exit
408 D/hsm1 ( 1999): mP2.exit
719 * the enter/exit calls and placing any deferred messages
752 * If transitionTo has been called, exit and then enter
754 * enter and exit methods to use transitionTo.
758 if (mDbg) Log.d(TAG, "handleMessage: new destination call exit");
762 * to know if enter/exit use transitionTo.
768 * Determine the states to exit and enter and return the
769 * common ancestor state of the enter/exit states. Then
770 * invoke the exit methods then the enter methods.
913 * Call the exit method for each state from the top of stack
921 curState.exit();
1249 * from processMessage the current state's exit will
1267 * from processMessage we will exit all current