cyrilmottier / polaris Goto Github PK

Hi,

in MapCalloutDrawable.java you have method in which you are getting mLeftCapDrawable width rather than height

@Override
public int getIntrinsicHeight() {
    return Math.max(mLeftCapDrawable.getIntrinsicWidth(),
            Math.max(mBottomAnchorDrawable.getIntrinsicHeight(), mRightCapDrawable.getIntrinsicHeight()));
}

I have problem in "Polaris doesn't find current location" ...

@cyrilmottier
Hi,
I deployed my .m2 with links like maven-android-sdk-deploy and did all possiblities ot run the polaris2 mapv2 project.But still i am getting the following issues.Can any one please bring me to the right path in executing the polaris2 map.
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Polaris2 - parent .................................. SUCCESS [ 0.482 s]
[INFO] Polaris2 ........................................... FAILURE [ 0.399 s]
[INFO] Polaris2 - Sample .................................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2.434 s
[INFO] Finished at: 2014-12-11T14:37:20+05:30
[INFO] Final Memory: 9M/81M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project polaris2-lib: Could not resolve dependencies for project com.cyrilmottier:polaris2-lib:apklib:1.0.0: The following artifacts could not be resolved: android.support:compatibility-v4:jar:13, com.google.android.gms:google-play-services:apklib:7, com.google.android.gms:google-play-services:jar:7: Failure to find android.support:compatibility-v4:jar:13 in https://repo1.maven.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn -rf :polaris2-lib

---If possible please provide me steps to reproduce for the working of this project.

Polaris is intended to make the developer's life easier. Providing default resources is a great way to avoid painful photoshopping for developers.

The idea here is to bring and enhance the MapPinDrawable concept introduced in a previous library of mine called GreenDroid (see https://github.com/cyrilmottier/GreenDroid/blob/master/GreenDroid-GoogleAPIs/src/greendroid/graphics/drawable/MapPinDrawable.java for more info)

com.cyrilmottier.polaris.internal.OverlayContainer -> MagnetoCallback -> onSinpleTap

How to reproduce:

1. Zoom in towards a marker;
2. While the new tiles are loading and you still get interpolated, scaled up tiles, move the map away from the marker you're zooming in.

This is what will happen:

http://img266.imageshack.us/img266/5526/device20121026092905.png

The blue marker was supposed to be over Los Angeles. After finish loading the tiles for that zoom level, everything is fine. This is the demo app downloaded from Google play.

Polaris currently contains only xhdpi resources. Technically speaking, this is not really a problem because the system automatically scales the resources to fit the display density. However, system scaling can produce blurry and inaccurate which results in a not-so-polished map.

The best solution is to create resources for all of the supported densities

I have added an Annotation object with title / subtitle to the mapview
I can click on the marker and the calloutview is correctly displayed.

The onAnnotationClicked callback is correctly called when I click on the calloutView.

In the onAnnotationClicked method, I would like to close this current calloutview.
For that, I'm using:
the calloutView.dismiss(Boolean.FALSE);

The callout is correctly closed but I need to wait several seconds before he could be displayed again...

Is it due to a wrong method call to close the callout view ?

I couldn't find a way to get the location of MyLocationOverlay marker. For the time being, I hacked this into PolarisMapView. Not sure if this is omitted on purpose but since PolarisMapView wraps MyLocationOverlay into it so I think adding this will simplify the usage a little bit. Or should we rely on LocationListener instead?

/**
 * Return current location of {@link MyLocationOverlay}.
 * @return GeoPoint or null if disabled.
 */
public GeoPoint getMyLocation(){
    if(mMyLocationOverlay != null){
        return mMyLocationOverlay.getMyLocation();
    }
    return null;
}

If the user clicks on an annotation a callout appears.
If the annotation is removed before than the callout has been removed (ie if the user doesn't click on the map), the callout will not disappear while clicking on the map. It will be dismissed only when the user clicks on another annotation, in which case a new callout will be displayed.

This happens frequently while using OnRegionChangedListener (or onRegionChangeConfirmed) for lazyloading:

• the user click on an annotation
• the user scrolls the map
• annotations are recreated
• an orphan callout is born.

What about Maven? I see you don’t use it, but who knows… :-)

It would be perfect to push the library to Maven Central of course, but Polaris uses Google Maps SDK which doesn’t exist in Central, so pushing isn’t possible yet.

Hello Cyril,

I've been trying Polaris on one app of mine, and I found, when adding it to my project, that you where implementing the function setBackground overriding it from ViewGroup in the class MapCalloutView.

Eclipse recommended me to delete de @OverRide tag, because there was no such function in parent class.

I don't know why is this, if it is a bug from Polaris library, or a bug from Eclipse.

See you, and thank you!

I do not consider hard-coding overlay order to be a good idea. If I add something besides annotations this something is drawn above annotation markers which generally is not desired. I had to change mOverlays.get() method to fix it. It's better to return to normal list behavior or to add an option to change predefined order.

It would be nice if an listener could be added that would fire on a basic Map simple tap, similar to the onTap method of the existing Overlay class.

This happened to me with the sample app, but clearly is coming from the lib itself.

Here is how to reproduce it:

• Open the app
• Move the map so that the New York marker is on the far right, where you can barely see it.
• Click on the New York marker.
• The map scrolls all the way to the right to come back almost were it was.

I would expect it to only scroll a few pixels to the left, just to let the callout be visible.

I have tested this library with Android API 10 support and I have an error (see bellow).
Is this library available for API 10 ?

MapCalloutView
@OverRide
public void setBackground(Drawable background) {
oopsBackgroundModified();
}

I'm trying to use Polaris im my app. I've got problem with clearing markers.
The only thing is not working for me at the moment - clearing markers.

I'm using annotations.clear() (I'm using names from your sample).
I think there is small bug here.

annotations.clear() is only removing markers (without tooltips).

Let me show you this on some screens. This is my app. I'm showing some locations for my car (it works great).

Locations: https://dl.dropbox.com/u/6838779/Screenshot_2012-10-22-15-42-26.png

I'm trying to reload new annotations and markers for other car. It works, markers are reloaded but previous annotation is still on the screen.

See this: https://dl.dropbox.com/u/6838779/Screenshot_2012-10-22-15-39-40.png (this is view for other empty car).

How can I use this library with actionbarsherlock? i always get classnotfound when i extend SherlockMapActivity

Recently, Google Maps app added a feature that allows users to tap the map twice and drag the finger (keeping the finger on screen after the second tap) to zoom in/out. It enables users to use the map app with one hand only, since pinch-to-zoom is not a straightforward gesture to be performed when using only one hand.