Discussion Forums  >  Uncategorized

Replies: 4    Views: 214

aBeginner
Lost but trying
Profile
Posts: 16
Reg: Mar 29, 2011
Singapore
460
01/01/12 02:07 AM (14 years ago)

Driving Directions and Scrollable Menu-Buttons Screen

Hi, I seriously need help. Don't know what to google for the following 2 problems that my app is facing. I'm using vers. 1.5, and creating Android app using Eclipse. 1. When I click on the marker, I want to show driving directions. However, when I click on driving directions, Google Maps load with the start and end point being my current location. How to change the code to make it such that starting point is the current location, and ending point is the location that I have input in the map? 2. I saw a topic where the Menu - Buttons screen can scroll in Android. However, there is no solution.. How do I stop the screen from scrolling? Any help would be appreciated. Thank you all, and have a wonderful 2012 =)
 
David @ buzztouch
buzztouch Evangelist
Profile
Posts: 6866
Reg: Jan 01, 2010
Monterey, CA
78,840
like
01/01/12 03:22 AM (14 years ago)
There is not a known solution for preventing the Android button menu from scrolling. We looked into it awhile ago but never resolved it. Not sure how to advise here other than you doing some research and helping the gang figure out a solution? Our efforts have been focussed on plugins (not necessarily useful for v1.5 apps) so we've not done much with Android v1.5 recently. Pout face. Driving directions: This should work. I haven't heard anything like you described so maybe it's an easy fix? I do know that this will not work in the simulator. Knowing this, if it doesn't work on an actual device, maybe look at the LogCat console to see if it shows you anything useful when you tap the driving directions link. The LogCat output is super useful (use the 'warn' tab to filter the output to only show you the warnings) and we wrote loads and loads of code for this purpose alone - helping with degugging. All the ouptut for your app that shows in the LogCat console will begin with a ZZ prefix making it easier to distinguish between android messages and messages from your project.
 
David @ buzztouch
buzztouch Evangelist
Profile
Posts: 6866
Reg: Jan 01, 2010
Monterey, CA
78,840
like
01/01/12 03:24 AM (14 years ago)
Update: Maybe tinker with the idea here to see if you can get the scroller (Buttons are in a built in Android ScrollView widget) to stop scrolling? http://stackoverflow.com/questions/2229178/disable-scroll-view-action
 
aBeginner
Lost but trying
Profile
Posts: 16
Reg: Mar 29, 2011
Singapore
460
like
01/01/12 07:24 AM (14 years ago)
Thank you so much. Will give it a try later =)
 
aBeginner
Lost but trying
Profile
Posts: 16
Reg: Mar 29, 2011
Singapore
460
like
01/09/12 02:49 AM (14 years ago)
For the driving directions, I think I know where the problem is. Sorry, but I am not good with the codes. Here is the section I believe there is a problem. if(tmpLatitude.length() > 3){ try{ //currentDevice.location > Obj_MapLocation.location BT_item tappedLocation = (BT_item) childItems.get(selectedIndex); Uri uri = Uri.parse(http://maps.google.com/maps?saddr= + tmpLatitude + , + tmpLongitude + &daddr= + tmpLatitude + , + tmpLongitude); Intent intent = new Intent(android.content.Intent.ACTION_VIEW, uri); I believe the problem is that tmpLongtitude and tmpLatitude are the values used in &daddr=. I already have a few screens with values of the Latitude and Longtidues of the location. So what are the variables to use in daddr= ? Do I have to declare the values? Please advise. Thank you =)
 

Login + Screen Name Required to Post

pointerLogin to participate so you can start earning points. Once you're logged in (and have a screen name entered in your profile), you can subscribe to topics, follow users, and start learning how to make apps like the pros.