Code Monkey home page Code Monkey logo

google-maps-utility-library-v3-read-only's People

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

google-maps-utility-library-v3-read-only's Issues

Token support

Hello, how to add token param to new gmaps.ags.TileLayer when my arcgis tile layer requires token ?

Thank you

Markers with label not showing in google chrome after deploying on IIS production

My application is using markerwithlabel library.It works well while in development environment on google chrome.But after deploying the application on IIS production , the markers are not visible in google chrome while they are visible in IE and Firefox.Please suggest a solution as most of the users are having google chrome installed on their machine.

Issue 24: MarkerWithLabel : problem of overlapping labels when two markers are in the same position

On your google repo

https://code.google.com/p/google-maps-utility-library-v3/issues/detail?can=2&start=0&num=100&q=&colspec=ID%20Type%20Status%20Priority%20Fixed%20Owner%20Summary%20Stars&groupby=&sort=&id=24

someone suggested a fix for the problem of overlapping labels

I found only one solution: (version 1.10)
instead of
line 141:
this.getPanes().overlayImage.appendChild(this.labelDiv_);
use this:
this.getPanes().markerLayer.appendChild(this.labelDiv_);

The overlayImage pane is pane which every elements overlay the any element of image and marker layer.

Because z-index work only in theier stack context, so any change of z-index can't solve this problem. Onle when you add the label and marker image to same pane, you can work with z-index.

Currently it's work for me.

Is there a reason this isn't implemented yet?

[enhancement] Add missing bower.json.

Hey, maintainer(s) of printercu/google-maps-utility-library-v3-read-only!

We at VersionEye are working hard to keep up the quality of the bower's registry.

We just finished our initial analysis of the quality of the Bower.io registry:

7530 - registered packages, 224 of them doesnt exists anymore;

We analysed 7306 existing packages and 1070 of them don't have bower.json on the master branch ( that's where a Bower client pulls a data ).

Sadly, your library printercu/google-maps-utility-library-v3-read-only is one of them.

Can you spare 15 minutes to help us to make Bower better?

Just add a new file bower.json and change attributes.

{
  "name": "printercu/google-maps-utility-library-v3-read-only",
  "version": "1.0.0",
  "main": "path/to/main.css",
  "description": "please add it",
  "license": "Eclipse",
  "ignore": [
    ".jshintrc",
    "**/*.txt"
  ],
  "dependencies": {
    "<dependency_name>": "<semantic_version>",
    "<dependency_name>": "<Local_folder>",
    "<dependency_name>": "<package>"
  },
  "devDependencies": {
    "<test-framework-name>": "<version>"
  }
}

Read more about bower.json on the official spefication and nodejs semver library has great examples of proper versioning.

NB! Please validate your bower.json with jsonlint before commiting your updates.

Thank you!

Timo,
twitter: @versioneye
email: [email protected]
VersionEye - no more legacy software!

Is optimized = false really necessary when calling google.maps.Marker?

I totally understand that optimized rendering isn't implemented in the MarkerWithLabel class but is it necessary to force this option to be false when calling google.maps.Marker? It significantly slows down the native rendering (from 0-1ms to 20-60ms per marker) and to my knowledge shouldn't break the default behavior of MarkerWithLabel when set to true.

In my project I use transparent 1x1px gifs as icons for the Marker and utilize only the MarkerWithLabel.label as a visible marker on the map. Whether or not the transparent pixels are "optimized" when rendered should not affect me.

MarkerWithLabel - ZIndex issue because of the different panes for label and pin

The Z-Index for the MarkerWithLabel does not work properly because the marker is pushed to "markerLayer" pane and the lablel is pushed to "overlayImage" pane.Because of this difference the label and marker will Stick together.

  • One possible solution would be to push the label to the same pane as the marker: "markerLayer"

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.