Orientation change and setRender

by qwesthead » Fri, 20 May 2011 15:38:29 GMT


Sponsored Links
 I've a region on an activity that uses GLSurfaceView. When the
Activity is resumed, I call the setRenderer and then the content of
the screen. They work fine. But, the problem arise when I change
orientation (configurationChange.) Upon orientation change, I need to
change the layout. After orientation change, surfaceChanged is getting
called. However, even when I call GLSurfaceview.requestrender,
Renderer.onDrawFrame is not getting called.
What are all the things I need to do when there is an orientation
change.

-- 



Other Threads

1. How to make my own apk installer?

Hi, all

Is it possible or not?
I need my own installer to implement apk autoupdate function.
or Can I use pkg installer without user confirm message(verbose mode)?
Any ideas?

Thanks,
BM

--~--~---------~--~----~------------~-------~--~----~

2. AsyncTask vs Handler/Looper

Hi All,

I'm trying to get my head around available Android's concurrency
blocks. I have extensive experience on related subjects from the java
enterprise world, so you can shoot low-level tech details at me no
prob :)

So, AsyncTask is to be executed only once. My understanding, on the
other hand, is that a handler/looper combination can be instantiated
once and be fed messages, either once or scheduled. Given that android
performance guide advises against excessive object creation, the
confusion is natural.

Is my general understanding of differences between subj 2 correct?
Basically, AsyncTask provides a great deal of simplicity/readability
into one's code sacrificing some resources (potentially), while
Handler can be tuned more, but is just a less convenient option?

Thanks in advance!
Andrew

--~--~---------~--~----~------------~-------~--~----~

3. A

4. ListView inside LinearLayout inside ScrollView

5. How to run the program on the new SAMSUNG GALAXY under windows XP

6. Playing video as a raw resource

7. Android Service Problem