What? Why would a restart of your Activity be a problem while waiting
for an HTTP response? You DO have the HTTP response in a separate
thread and Service, don't you?
On Jul 16, 3:41 pm, Brad bradfull...@gmail.com wrote:
Hi,
I'm trying to lock my activity to the current orientation to prevent
I wouldn't suggest putting it in a Service unless it is really something you
want to have executing when the user is outside of your app.
For example, a browser typically wouldn't associate a Service with
networking, because all of its networking is there to serve the UI.
On Mon, Jul 18, 2011 at
Note that basically everything you do for dealing with a configuration
change is *exactly* the same thing you need to do to correctly handle your
app being killed in the background if the user has (temporarily) left its
UI. Thus making sure you deal correctly with a config change is a really
good
Dianne, thanks for the response - you're probably right, I should just
bite the bullet.
I'd like to vent a little though about what a hassle it is to deal
with orientation changes. It must be the #1 source of bugs in the
apps that I've come across (including my own apps). iOS does a lot
of
4 matches
Mail list logo
