I've coded this too in my first app (EmailAlbum Viewer) which displays
pictures contained in archives that are received by email, for
example.
If someone receive pictures which are too large for the app memory, I
prefer catching the error and display an informative message to the
user rather than an ugly default application shutdown.
Nivek
On 23 août, 19:07, Streets Of Boston <flyingdutc...@gmail.com> wrote:
> Depends...
>
> In general, it's no good catching Errors. But I'm using this
> particular error to see if i have enough memory for creating a full-
> sized bitmap (no other way of doing this). If not, i catch the
> outofmemoryerror and will use a smaller sized bitmap.
>
> On Aug 23, 5:02 am, alex <gsm...@gmail.com> wrote:
>
>
>
> > I guess you are trying to perform manipulations on a byte[]. Just use
> > decodeStream(...) or decodeFile(...) instead. Cathing runtime errors
> > is plain wrong.
>
> > On Aug 23, 2:45 am, Bob <bshumsk...@yahoo.com> wrote:
>
> > > Hi,
> > > I am getting an outofmemory error (java.lang.outofmememoryerror) from
> > > a bitmapfactory that doesn't seem to be caught despite the fact that
> > > it is in a try{ }catch block. Can I catch this error somehow or is it
> > > outofmemory inherently uncatchable?
>
> > > Thanks,
> > > Bob- Hide quoted text -
>
> > - Show quoted text -
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
