At JAXConf, Romain Guy did say that instantiating Paint is a
surprisingly CPU intensive operation. So yes, that should certainly be
taken out of the for loop. The suggestion of taking out doubleParse()
is a good one, too.
On Jun 28, 5:33 pm, JP wrote:
> On Jun 27, 7:32 am, Boozel wrote:
>
> > Ca
Thanks, it was happening very intermittently but this seems to have helped.
--
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
On Jun 27, 7:32 am, Boozel wrote:
> Can any one tell me what the best structure is to do the drawing and prevent
> this?
Your draw() routine is inefficient, and you really get hit in the
constrained mobile environment. Here's a few changes that I would try:
- Pull object instantiations out of t
On Jun 28, 8:12 am, Dianne Hackborn wrote:
> Do "adb shell cat /data/anr/traces.txt" to see what your app was busy doing
> at that point.
Seriously, we need a blog entry that describes all these useful
debugging tidbits.
--
You received this message because you are subscribed to the Google
Gro
4 matches
Mail list logo
