@Agus: Sure, I'll probably want to register some intent filters some time (actually, all my applications so far have been such that just using the SpecificActivity.class Intent constructor has been appropriate...so no intent filters), but how would automatic Activity registration impede the creation of intent filters in the future?
@Andrew: Thanks, I'll keep AliasActivity in mind. @Joba: That does sound like a good tool (all the features you mentioned specifically) but I think I would be hesitant to try to learn a new dev environment; getting all the idiosyncrasies of Android in Eclipse was a respectable learning curve for me. And, once learned, it seems to be quite a good platform...currently minus maddening difficulties with trying to load GPX files in the DDMS view: http://groups.google.com/group/android-developers/browse_thread/thread/b1d0e29b704d51ab/6f908be1b4ee7fea --Ben On Sep 5, 10:50 am, Joba Chamberlain <[email protected]> wrote: > > Is there a reason Google wouldn't want to automatically register any > > class inheriting Activity in the manifest as an Activity? > > > As I wrote in my original message, the Activity equivalent to Test > > will eventually have GUI elements (a Button, for example) whose events > > will trigger SecondActivity; for now, I want to skip that and just > > develop SecondActivity. So the behavior you describe is exactly what > > I'm after (for now). > > Have you tried using motodevstudio for Android? It is built on Eclipse > and customized for Android. When you add a new activity it is > automatically referenced in the Manifest. You will still have to > specify intent-filters and whatnot, but it will prevent simple errors > like the one above. > > You can also easily on run/debug a specific activity, rather than the > main, with motodev. > > Try it out. It works great for me (outside of frequent emulator issues > - which I barely use). > > Paul > > On Sep 4, 9:05 pm, BJP <[email protected]> wrote: > > > Aha, you are indeed correct about registration in the manifest. > > > Is there a reason Google wouldn't want to automatically register any > > class inheriting Activity in the manifest as an Activity? > > > As I wrote in my original message, the Activity equivalent to Test > > will eventually have GUI elements (a Button, for example) whose events > > will trigger SecondActivity; for now, I want to skip that and just > > develop SecondActivity. So the behavior you describe is exactly what > > I'm after (for now). > > > Thanks again! > > --Ben > > > On Sep 4, 5:52 pm, "Mark Murphy" <[email protected]> wrote: > > > > > I have a skeleton system of Activities that will eventually be filled > > > > with GUI elements, but for now I just want to work on a particular > > > > aspect of the project without developing the initial GUI parts first. > > > > But, when I try to launch an Intent from onResume, I get a > > > > RuntimeException in ActivityThread.performResumeActivity. What is > > > > wrong with the following code? > > > > > public class Test extends Activity { > > > > @Override > > > > public void onCreate(Bundle savedInstanceState) { > > > > super.onCreate(savedInstanceState); > > > > setContentView(R.layout.main); > > > > } > > > > > public void onResume() { > > > > Intent i = new Intent(this, SecondActivity.class); > > > > this.startActivity(i); > > > > } > > > > > public class SecondActivity extends Activity { > > > > @Override > > > > public void onCreate(Bundle savedInstanceState) { > > > > super.onCreate(savedInstanceState); > > > > setContentView(R.layout.main); > > > > } > > > > } > > > > } > > > > What you are doing makes no sense. > > > > When the Test activity starts up, onResume() is called. At that point, you > > > start SecondActivity, so the user is presented with SecondActivity right > > > away. The user back-buttons out of SecondActivity, at which point > > > onResume() on Test gets called...starting up SecondActivity again. > > > > Do not call startActivity() in onResume(). Do it based on user input > > > (menu, button, list item click, etc.). > > > > Beyond that, look at your stack trace to find out the source of your > > > exception (use adb logcat, DDMS, or the DDMS perspective in Eclipse to get > > > the Java stack trace). Perhaps SecondActivity is not registered in your > > > AndroidManifest.xml file? > > > > -- > > > Mark Murphy (a Commons Guy)http://commonsware.com > > > Android App Developer Books:http://commonsware.com/books.html > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
