onActivityResult not being called in Activity that uses GLSurfaceView

by Streets Of Boston » Mon, 26 Apr 2010 21:59:24 GMT


Sponsored Links
 What are the launch-properties of your sub-activity?
Is it a 'singleTask' or 'singleInstance'? If so, the sub-activity
won't report a result to your main-activity's 'onActivityResult()'.

I ask this, because i was struggling with this same issue for a while
until i discovered that my sub-activity was set to 'singleTask'....




>



onActivityResult not being called in Activity that uses GLSurfaceView

by SChaser » Tue, 27 Apr 2010 12:05:02 GMT


 he sub-activity has the same characteristics when started by the map-
view activity, where it reports a result back, as when started by the
GLSurfaceView activity, where it does not report back. It is the same
sub-activity, started by the same code, with the same arguments to the
intent.

BTW, how do you set something "singleTask" or "singleInstance"? I
don't have a setting like either.

Thanks for your response!

SChaser

On Apr 26, 6:59am, Streets Of Boston <flyingdutc...@gmail.com> wrote:
> >


Sponsored Links


onActivityResult not being called in Activity that uses GLSurfaceView

by String » Tue, 27 Apr 2010 12:51:58 GMT


Other Threads

1. Facebook = Done ; Twitter = Pending ; Developers please guide

Hey guys
I have completed my quest over facebook to post a simple text ,
image , link in facebook.
Now i have to do the same for twitter, any word over this topic will
be appreciated .
Thanks

-- 

2. Problem passing array from vertex to pixel shaders

I've discovered a problem passing an array from a vertex shader to a pixel 
shader. Somewhere the array ends up overlapping with other constants, for 
example if I have an array of UV coordinates and a colour being passed 
though, then changing the UV coordinates will affect the colour. Using 
either the colour or UV alone works, I assume because the compiler optimises 
out the unused variables and prevents the overwrite occurring. This happens 
even with an array size of 1.

To give a simple example, this pixel shader will render incorrectly:

varying highp vec4 vl_TexCoord[1];
varying highp vec4 vl_Color;
uniform highp sampler2D _diffuseMap;
void main() {
   gl_FragColor = vl_Colo r* texture2D(_diffuseMap,  vl_TexCoord[0].xy);
}

However changing main to either of these cases work, giving either a 
correctly mapped texture, or correct vertex colour:

void main() {
   gl_FragColor = vl_Color;
}

void main() {
   gl_FragColor = texture2D(_diffuseMap,  vl_TexCoord[0].xy);
}

Changing the vl_TexCoord array to a simple vec4 makes the problem go away, 
so I have a workaround, but this seems like a fairly serious problem, 
possibly in the shader compiler.

The same issue was raised on gamedev so I think it's a genuine bug:
http://www.gamedev.net/topic/594352-gl-20-shader-varying-array-problem/

Has anyone else experienced this problem? I'm using a HTC Desire HD for 
testing, using the 2.2 Android SDK. I don't know if it's hardware or SDK 
version specific at the moment.

-- 

3. SIP Demo and Android 2.3 problem

4. how to disable the "Clear data" Button (Froyo)

5. How do certain application backup the APK files?

6. Development strategies

7. Adding Slide Button on Key lock screen