Mihai Fonoage wrote: > and I need to deal with > this case specifically, which complicates my application logic a > little (here though it is probably my fault - not a perfect design).
Your View should not care about how many times it is drawn. Relying on assumed behavior (e.g., onDraw() is only called in certain scenarios) is not safe. Otherwise, your code may break in future Android releases where your assumption is no longer valid. You are certainly welcome to figure out how to avoid onDraw() unnecessarily, but you really need to implement support for onDraw() occurring when you are not necessarily expecting it. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy _Android Programming Tutorials_ Version 1.0 In Print! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
