On Apr 19, 9:08 am, "~ TreKing" <[email protected]> wrote: > I don't know what you're asking. Activities don't really "run" like threads > that have a definite function that gets executed to do work. They have > functions that are invoked in response to system events (onCreate, onPause, > onConfigurationChanged, etc). ===================================================== Here is my 'model' that compares an embedded program to an android program: embedded program: main gets called by os, main calls initstuff(), falls into a while(1) loop that calls inputs(), process() and outputs() forever. The os can kill it if it has to. In the android program, the onCreate is the init, the os scheduler is the while(1) loop, and the onSensorChanged events are like the input and process functions, and the onDraw is like the output function. Sort of. Does this model make sense to anyone else? Can it be explained more clearly by another model?
-- You received this message because you are subscribed to the Google Groups "Android Beginners" group. NEW! Try asking and tagging your question on Stack Overflow at http://stackoverflow.com/questions/tagged/android To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en
