Ok, that makes a /major/ difference: The app actually gets started, and a centerpoint for the map appears. However, no map actually is shown. A diagonal crosshatch is there, but nothing else.
The app has some key responses dispatched by onKeyDown and these appear to basically be working correctly. So I need to be able to figure out what's happened to maps (between m5 & now). Thanks much. Ken On Sep 5, 6:39 pm, Mark Murphy <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: > > A) I tried adding (no luck) the following for the <uses-library> > > tag. Is this anywhere near correct? > > > <uses-library>com.google.android.maps</uses-library> > > Try: > > <uses-library android:name="com.google.android.maps" /> > > It should appear inside your <application> element. > > -- > Mark Murphy (a Commons Guy)http://commonsware.com > Warescription: All titles, revisions, & ebook formats, just $35/year --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Beginners" group. To post to this group, send email to android-beginners@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] Announcing the new M5 SDK! http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en -~----------~----~----~----~------~----~------~--~---
