I didn't see it, but I figured it by myself by looking at one of the API Demos. Indeed, I was calling it before setContentView() (didn't know I'm not supposed to). Thanks.
On Sep 17, 1:35 am, Marco Nelissen <[email protected]> wrote: > On Wed, Sep 16, 2009 at 3:27 PM, Felix Oghina <[email protected]> wrote: > > > My application dies (application has stopped unexpectedly blah blah) > > on this line (in my onCreate function): > > > requestWindowFeature(Window.FEATURE_INDETERMINATE_PROGRESS); > > > I know it's on this line because if I put a Log.d() before it shows, > > if I put it after, it doesn't. Also, my app was working perfectly > > before this change. Any ideas about why it would not work and crash > > like that? > > You don't need the Log.d to tell you where it crashes, since there > should be a full stack trace with linenumbers in the log already. > What else are you seeing in the log besides your Log.d ? My guess is > you're calling it too late (after setContentView), but that shows up > in the log I think, so you would have seen that. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
