Okay. I can accept that waiting until onActivityCreated() doesn't make
a significant difference. But I still shouldn't be doing disk I/O or
network accesses on the UI thread, right? On Honeycomb, a network
access on the UI thread is fatal (see Brad's blog post on StrictMode).
So I have to create a
Also, did you mean the time between my fragment's onAttach() and
onActivityCreated() is in the activity's onStart()?
- dave
On Feb 15, 8:48 pm, Dianne Hackborn hack...@android.com wrote:
This really won't gain you anything. The time between onAttach() and
onActivityCreated() is the time your
Never mind that last one. I'm logging lots of messages to understand
when things fire, and I saw my activity's onStart() message before I
saw my fragment's onActivityCreated(). But of course the activity is
in onCreate() in between. It just happens to get started with
onStart() before my fragment
You absolutely should not be doing networking or (major) disk IO on the main
thread, as has always been the case. HC has the new Loader API to help with
this, and of course there as been AsyncTask for a long time, etc.
On Tue, Feb 15, 2011 at 6:19 PM, davemac davemac...@gmail.com wrote:
Okay.
4 matches
Mail list logo
