I have found answers to this through other channels. The real answer is that you need to have an activity, not a native activity. If you have written a native activity already and don't want to change too much code you can derive from the java native activity class (which itself just derives from activity) and you don't have to change what you are doing. But your app is now a normal activity, not a native activity to Android.
In fact, you can't really paint yourself too far into a corner with native activity because you can always just do the trick above to switch you app without changing much of your code to a normal activity. Chris On Oct 22, 5:57 pm, chrisn <[email protected]> wrote: > This post was posted there in January with no response. > > http://groups.google.com/group/android-ndk/browse_thread/thread/9bbb4... > > So I am trying that group but my hopes aren't high. > > Chris > > On Oct 22, 2:45 pm, TreKing <[email protected]> wrote: > > > > > > > > > On Fri, Oct 21, 2011 at 1:07 PM, chris <[email protected]> wrote: > > > I am brand new to Android development so if I missed anything please point > > > me to documentation where I can get up to speed. > > > Try the NDK group. > > > --------------------------------------------------------------------------- > > ---------------------- > > TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago > > transit tracking app for Android-powered devices -- 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
