Hi Mark,

The stack trace is as follows:

W/System.err(  769): java.lang.Throwable: stack dump
W/System.err(  769):    at java.lang.Thread.dumpStack(Thread.java:610)
W/System.err(  769):    at <package_name>.SecondView.onDraw(SecondView
.java:381)
W/System.err(  769):    at android.view.View.draw(View.java:6274)
W/System.err(  769):    at android.view.ViewGroup.drawChild
(ViewGroup.java:1526)
W/System.err(  769):    at android.view.ViewGroup.dispatchDraw
(ViewGroup.java:1256)
W/System.err(  769):    at android.view.ViewGroup.drawChild
(ViewGroup.java:1524)
W/System.err(  769):    at android.view.ViewGroup.dispatchDraw
(ViewGroup.java:1256)
W/System.err(  769):    at android.view.View.draw(View.java:6277)
W/System.err(  769):    at android.widget.FrameLayout.draw
(FrameLayout.java:352)
W/System.err(  769):    at android.view.ViewGroup.drawChild
(ViewGroup.java:1526)
W/System.err(  769):    at android.view.ViewGroup.dispatchDraw
(ViewGroup.java:1256)
W/System.err(  769):    at android.view.ViewGroup.drawChild
(ViewGroup.java:1524)
W/System.err(  769):    at android.view.ViewGroup.dispatchDraw
(ViewGroup.java:1256)
W/System.err(  769):    at android.view.View.draw(View.java:6277)
W/System.err(  769):    at android.widget.FrameLayout.draw
(FrameLayout.java:352)
W/System.err(  769):    at com.android.internal.policy.impl.PhoneWindow
$DecorView.draw(Pho
neWindow.java:1883)
W/System.err(  769):    at android.view.ViewRoot.draw(ViewRoot.java:
1332)
W/System.err(  769):    at android.view.ViewRoot.performTraversals
(ViewRoot.java:1097)
W/System.err(  769):    at android.view.ViewRoot.handleMessage
(ViewRoot.java:1613)
W/System.err(  769):    at android.os.Handler.dispatchMessage
(Handler.java:99)
W/System.err(  769):    at android.os.Looper.loop(Looper.java:123)
W/System.err(  769):    at android.app.ActivityThread.main
(ActivityThread.java:4203)
W/System.err(  769):    at java.lang.reflect.Method.invokeNative
(Native Method)
W/System.err(  769):    at java.lang.reflect.Method.invoke(Method.java:
521)
W/System.err(  769):    at com.android.internal.os.ZygoteInit
$MethodAndArgsCaller.run(Zygo
teInit.java:791)
W/System.err(  769):    at com.android.internal.os.ZygoteInit.main
(ZygoteInit.java:549)
W/System.err(  769):    at dalvik.system.NativeStart.main(Native
Method)

I have a LinearLayout that contains the Chronometer (+ some TextViews
all in another LinearLayout), and the SecondView view. I guess the
problem is that all child views (Chronometer + SecondView) of the root
LinearLayout view are updated in case one of its child views
(Chronometer) gets updated (there is no concept of partially updating
the screen?). Should it be like this. Since I haven't changed anything
in my second view, it should not be re-drawn. The problem is that this
is out of my control. There is nothing I can do to stop the second
view of being re-drawn.

Mihai Fonoage

On Oct 30, 8:35 am, Mark Murphy <mmur...@commonsware.com> wrote:
> Mihai Fonoage wrote:
> > Any help on this issue is greatly appreciated.
>
> Your question cannot be answered in the abstract. You need to find this
> out for yourself.
>
> Put a breakpoint or dump a stack trace in onDraw() of your second view.
> Figure out from there what is triggering it. If I had to guess, it is
> being triggered somehow through whatever layout contains both your view
> and the Chronometer.
>
> --
> Mark Murphy (a Commons 
> Guy)http://commonsware.com|http://twitter.com/commonsguy
>
> Android Development Wiki:http://wiki.andmob.org
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to