History log of /frameworks/base/core/java/com/android/internal/util/StateMachine.java
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
bbf30dfd767f823f5f40d14b498e2a593454c5c9 29-May-2012 Wink Saville <wink@google.com> Enhance StateMachine Quitting and logging support.

Make StateMachine#quit non-conditional and remove the need to
process the SM_QUIT_CMD it is now private.

Rename halting to onHalting.

Add onQuitting

Change the message specific logging to be more generic and change
the xxxProcessedMessagesYyy methods to xxxLogRecXyy names. Also add
addLogRec(String) and addLogRec(String, State) as the generic logging

bug: 5678189
Change-Id: I22f66d11828bfd70498db625fe1be728b90478b7
583eaaa57c51b28bf14da2a5cc94a2e6091cccf5 14-Apr-2012 Wink Saville <wink@google.com> Enhance the debug output for StateMachines.

Allow some messages to be ignored and allow the subclass to
add additional information. In particular, the information
can be used to decode the msg.what to a string.

Change-Id: I4f53becc6f0cb77399f99702084efef9d8785d67
cea056f5894543819898a0e62f98dc7870b27758 27-Mar-2012 Wink Saville <wink@google.com> Add SM_INIT_CMD.

The enter methods of the initial states are now executed
in response to a message and therefore run in the handler
associated with the StateMachine. Previously these would
run in the thread that start() was called from.

I ran into a problem where in an Activities onCreate I called
StateMachine#start(), which called the default states enter,
which invoked Context#bindService. But bindService never
completed because onCreate hadn't returned. But invoking the
enter methods on the StateMachines handler this problem does
not occur.

Change-Id: I2c2e52e5de29a987c098196a0efdba446cbc29d0
f76a50ce8fdc6aea22cabc77b2977a1a15a79630 09-Mar-2012 Ken Wakasa <kwakasa@google.com> Fix obvious typos under frameworks/base/core

Change-Id: Ia5fc3db1bb51824e7523885553be926bcc42d736
a544d467f2a876f2ada2880214b3157cfaef769f 07-Dec-2011 Jaikumar Ganesh <jaikumar@google.com> Reduce likelihood of crash in state machine.

Reduce likelihood of crash when state machine has quit and someone
sends a message using one of the public functions.

Bug: 5724844

Change-Id: I6582a1d19113e6ed545c8ab20adb0a414d8784a7
6f9a61651e7949a5d63a4b44314d435c0105a51f 28-Nov-2011 Jaikumar Ganesh <jaikumar@google.com> Cleanup static references when quitting.

The State machine was leaking references when it was
getting created and destroyed.

Change-Id: I7904baf0482eef1617071d159d7b283566b4095c
d2fe04b71a89a0608eb7c67065dead2a1f540122 22-Jul-2011 Isaac Levy <ilevy@google.com> Rewrote DnsPinger - now is async and concurrant

Change-Id: I93e1374ae857832935202614e34ce18f040fcfc7
64c42cae4482fe0157e977b8ddd0f2c2436b3f31 18-Apr-2011 Wink Saville <wink@google.com> Rename HierarchicalStateMachine and HierarchicalState to StateMachine and State.

Change-Id: Ib4b33894da75f5f156066092fb145b478e52f7d7