-
Notifications
You must be signed in to change notification settings - Fork 91
Fix #449 - Targeted latest API version and updated looks using new API o... #460
base: master
Are you sure you want to change the base?
Conversation
…sing new API options and removing options-button menu.
@vreixo Thanks for this PR, and sorry for the long delay reviewing this. I've been tied up in a number of things. I hope to get back to reviewing this over the next week or so. |
@vreixo Finally getting around to this - if I run the code as-is (minus a conflict or two in build.gradle that is easy to resolve), I get:
Looks like you moved But reverting this code to its original position above Do you recall getting this error, or why you moved |
Looking at some of the other changes that are related to main.xml on different screen densities/sizes, I'm guessing that this has something to do with the LG G3 w/ Android 5.0 I'm testing on and a map XML element missing from a main.xml file? In Android Studio here are the implementations of main.xml I see: I'll see if I have time to look at this further later. |
There is also a chance that this is related to using the newest Android Support library with the old Google Play Services for Froyo, since that also changed in this PR (i.e., the Android Support library version was bumped to newest). |
Hi @barbeau! Has been a while since I have done this and, unfortunately, I I'll probably have some time these days to take a look and to see the lines
|
Add a Gitter chat badge to README.md
… latest plugins/libraries In the process of looking to fix CUTR-at-USF#477, we need to change minSdkVersion to 9 to use the android-maps-util library. This also means increasing the Google Play Services version to the latest, which means we have to fix CUTR-at-USF#320 to switch from the LocationClient to FusedLocationApi. Also bumps the Android Gradle Plugin version and support library vresion to match our compileSdkVersion. Also removes an unused PNG file that was flagged by the Gradle plugin as an invalid name (it includes a ".").
…calculations * Our code for bounding box calculations was complex to handle the scenario where a bounding box crosses the IDL. However, apparently there was at least one bug, as the point (28.05866283764341,-82.41802878677845) wasn't detected as within the bounding box (24.5454892,-124.16933,49.273757,-69.965541). * To avoid maintaining this complex code, I'm switching to using the android-maps-util, which has a PolyUtil.containsLocation() method. I've also added a test for the case that was previously failing. Currently all bounds test pass when using the android-maps-util library. * PolyUtil.containsLocation() does NOT include a tolerance parameter, while our old code did. So, I've removed the tolerance parameter from our code. We'll see if this causes any problems in real world scenarios.
* This avoids including a bunch of code we're not using, and also avoids adding more permissions we don't need in the manifest.
It appears to have been working again for at least months (circa beginning 2015)
…for-Android # Conflicts: # gradle/wrapper/gradle-wrapper.properties # opentripplanner-android/build.gradle
Hi @barbeau ! I have updated this branch and gradle file and on my nexus 5 with 6.0.1 is working ok. If it would pass Travis and work for your tests would be great to launch another update! |
@vreixo Awesome, great to see you working on this again :)! To get Travis to build, you'll need to update the If you push that commit here it should trigger Travis to rebuild. |
Also, could you please rebase your branch on the current master? Looks like some of my commits snuck into this PR. |
You'll also need to force-push to your remote branch on Github to erase the current commits in this PR, and start over with your new rebased commit. |
Great! I'll update my branch. Btw, could you update the spreadsheet |
@vreixo Sure, just updated it. |
|
...ptions and removing options-button menu.