Andreas, Thanks an excellent point. I was fixated on the 50KB part and not thinking about it being unrolled in memory and having to work with the actual bits. That makes perfect sense. I was working last night on an image that was fairly large. I found that making it smaller helped until it finally loaded. I found googling some mentions to 300 KB files being the upper limit for display but was looking to verify that and not take it on faith. Your explanation is much more plausible.
Wally > Date: Wed, 25 Jan 2012 00:29:42 -0800 > From: [email protected] > To: [email protected] > Subject: Re: [mono-android] upper limit on resources/drawable size? > > Hi, > > I do not know whether there is an upper limit to the file size, but you have > to keep in mind that a JPEG file with a pixel size of 1000x1000 that is > maybe only a 50 KB file, will require 3 MB (1000x1000x3) when loaded. > Therefore I am more concerned with the resulting pixel size of images, then > with the compressed image file size. Just my thoughts. > > Andreas > > > -- > View this message in context: > http://mono-for-android.1047100.n5.nabble.com/upper-limit-on-resources-drawable-size-tp5429392p5429700.html > Sent from the Mono for Android mailing list archive at Nabble.com. > _______________________________________________ > Monodroid mailing list > [email protected] > > UNSUBSCRIBE INFORMATION: > http://lists.ximian.com/mailman/listinfo/monodroid
_______________________________________________ Monodroid mailing list [email protected] UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
