This looks like it does what I have been trying to do ... except that I have
no way of knowing if it will resolve the problem that occurs when I call the
listview until I tinker with it. I have things running well enough except
for this problem (thus I am inclined to continue with what I have and
Not to beat a dead horse ... but other suggestions regarding how to
deal with the mis-registered list view issue would be super
appreciated. My app is a data visualization app like Google Maps and
I was using the SurfaceView mainly in order to better control the draw
loop (like what is described
Solved ... the culprit was trying to run without the window background
via :
http://android-developers.blogspot.com/2009/03/window-backgrounds-ui-speed.html
It seems that this theme speed may speed up my surfaceView but screws
up my lists.
This cost me a lot of frustration to sort out. I hope
This will have no impact on SurfaceView, since by design it gives you a
dedicated surface that you control all of the pixels for and so the window
background will never be drawn in it. (That said, it does have an impact on
drawing in the main window, if you have places that aren't filled by the
Does GLSurfaceView do what you want? See the latest blog post.
--~--~-~--~~~---~--~~
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
Perhaps this would be a better way to inspire feedback. Is it
possible to pause and resume a view based upon SurfaceView? What
would be the correct way to restart the view so that the thread can
begin drawing again?
On Fri, Apr 24, 2009 at 1:29 PM, Jason Van Anden
6 matches
Mail list logo
