Hey Everybody. I am typically comfortable with using google's Android App inventor concerning this problem, but this designer seems almost too graphically driven. My question is, how can I get the user's current location (i.e, latitude and longitude) and then rewrite this as the lat/long input for the multiple-locations map? The idea is I want the user to be able to click a button and locate specific businesses nearby; obviously I need their current locations to factor in so that the search results will be relevant! I understand this may be something that needs to be edited in the source code, and if that is the case I suppose I'll cross that bridge when I get to it. Thank's for the help everyone! -Dan

this designer seems too graphically driven - are you referring to App Inventor (which I have never used) or buzztouch? If you're referring to buzztouch, great, thats exactly what we're trying to do ;-) You'll have a great deal of trouble doing what you describe after downloading your source-code unless you have a deep understanding of Java and the Android SDK. It's probably a matter of building a new Activity (Android term for a View or Screen) that does what you want. The buzztouch map-view isn't designed to do this, it's designed to show one or a series of pre-determined locations (like businesses, churches, schools, etc). Typically these locations are important to the app's owner and they need a way to show them on a map.

Hi David, Yes, I am referring to the App Inventor, and it's a pretty useful tool overall, other than some drawbacks with the ability to re-orient objects present in the app (buttons, menus, etc). Unfortunately, I need a way to dynamically interpret the user's location for the app I am attempting to design :-( It's too bad, I love buzztouch's easy to use interface and it's clarity concerning types of jobs, but I need the functionality that App Inventor offer's on this issue (although not without plenty of bugs itself!) I really appreciate the answer though: looks like i'll have to find a middle of the ground solution! It might not be a bad thing for buzztouch to include in some future version. Thanks again! -Dan