On Jan 26, 2:53 pm, Mark Murphy <mmur...@commonsware.com> wrote: > I would recommend that developers depend as little as possible on > explicitly using firmware-defined resources. If you need them, copy > their values into your project. Or, at least have a value that you use > as a fallback in case a firmware-defined resource is not available.
While I understand that sentiment, it's not practical. Widgets like Button constantly use built-in firmware-defined resources. And I too have gotten TWO crash dumps where the .inflate() failed unexpectedly, one trying to fetch Button's .9.png background, and one trying to fetch a custom .9.png that I had put into my own app, just as you suggest doing. Now my first guess was that I was doing something wrong with a timer, some accidental UI Thread/Worker Thread collision, so I did revise that area of the code. But if it wasn't that, then I am not sure exactly how you should really respond to an exception deep in .inflate() or .setContentView()... besides calling .finish() and let the user wonder why the activity did not appear. -- 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
