> I'm just learning -- no particular task in mind -- but I'm thinking of
> a case where, for the sake of argument, I'd put up three successive
> dialogs, to gain pieces of information to be returned to the main
> activity. I can see how you could do it by having the onClicked from
> one dialog kick off the next bit of logic and so on, but that really
> chops up the "main program" logic vs having it all in a single
> sequence with "calls" out for the dialogs.
You are going to have to live with "chopped up" logic, then. Android
does not offer a blocking UI model.
--
Mark Murphy (a Commons Guy)
http://commonsware.com | http://github.com/commonsguy
http://commonsware.com/blog | http://twitter.com/commonsguy
_The Busy Coder's Guide to Android Development_ Version 3.1 Available!
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
No comments:
Post a Comment