[android-developers] Re: onActivityResult not being called

2012-03-25 Thread mcterry
That's correct, using standard should trigger the OnActivityResult() Are you still having trouble getting the result? On Friday, March 23, 2012 12:04:32 PM UTC-4, Joey Selah wrote: Thanks Matt! The resultCode == 0 is nothing really, I just quickly threw it in so I could set a breakpoint

[android-developers] Re: onActivityResult not being called

2012-03-25 Thread Joey Selah
I switched the launch mode for BaseIngredientEdit to standard and still nothing. What am I missing? If I got some free time tomorrow I'm going to try to make a sandbox project with just skeleton code to get OnActivityResult() to trigger for me to compare against. Any ideas in the mean time? On

[android-developers] Re: onActivityResult not being called

2012-03-23 Thread Joey Selah
Thanks Matt! The resultCode == 0 is nothing really, I just quickly threw it in so I could set a breakpoint to test that the event handler was being called and the breakpoint isn't hitting. but I'll definitely be changing resultCode after it hits. So correct me if I'm wrong, if I set the launch

[android-developers] Re: onActivityResult not being called

2012-03-22 Thread Joey Selah
Actually excuse me, I've mixed the classed up some how. Below is the correct code: public class BrewJournalEdit extends Activity { @Override protected void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState);

[android-developers] Re: onActivityResult not being called

2012-03-22 Thread mcterry
Hey Joey - first off, it looks like you are testing for the resultCode == 0 in your onActivityResult() method. You should be looking for whatever you set your result to in your BaseIngredient Activity (looks like you're using RESULT_OK). In addition, if you've changed the launchMode of an

[android-developers] Re: onActivityResult not being called

2012-03-20 Thread FiringCode
Intent().setClass(BrewJournalEdit.this, BaseIngredientEdit.class); to Intent().setClass(BaseIngredientEdit.this, BrewJournalEdit.class); -- 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] Re: onActivityResult not being called

2012-03-20 Thread FiringCode
Below code is some odd. Intent().setClass(BrewJournalEdit.this, BaseIngredientEdit.class); How about changing to below code? Intent().setClass(BaseIngredientEdit.this, BrewJournalEdit.class); 2012년 3월 20일 화요일 오후 12시 1분 48초 UTC+9, Joey Selah 님의 말: I'm having an issue where the

[android-developers] Re: onActivityResult not being called in Activity that uses GLSurfaceView

2010-04-26 Thread Streets Of Boston
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

[android-developers] Re: onActivityResult not being called in Activity that uses GLSurfaceView

2010-04-26 Thread SChaser
The 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,

[android-developers] Re: onActivityResult not being called in Activity that uses GLSurfaceView

2010-04-26 Thread String
On Apr 27, 5:04 am, SChaser crotalistig...@gmail.com wrote: BTW, how do you set something singleTask or singleInstance? I don't have a setting like either. http://developer.android.com/guide/topics/manifest/activity-element.html#lmode String -- You received this message because you are