gmaps.events
Advanced tools
gmaps.js module to manage native and custom events.
For using with bundlers (as Browserify or Webpack):
npm install gmaps.events --save
Before require() this module you need to require('gmaps.core').
For using directly in the browser, download the gmaps.events.js (or gmaps.events.min.js) in dist.
You need to register a <script> tag with the Google Maps JavaScript API, then import gmaps.core.
Every Google Maps map needs a container (<div id="map"></div> in this demo), which needs to have width and height, and be visible (without display: none, for example):
<!DOCTYPE html>
<html>
<head>
<title>Test</title>
<script src="http://maps.google.com/maps/api/js?sensor=true"></script>
<script src="gmaps.core.js"></script>
<script src="gmaps.events.js"></script>
<style type="text/css">
#map {
width: 400px;
height: 400px;
}
</style>
</head>
<body>
<div id="map"></div>
<script>
var map = new GMaps({
el : '#map',
lat: -12.0433,
lng: -77.0283,
zoom: 12
});
map.on('click', function() {
console.log('Map clicked');
});
</script>
</body>
</html>
For more examples you can check the tests in this repo.
on(eventName, scope, handler)Create a new event listener and attach a handler function to a scope, which can be a google.maps.* object that supports events, or a GMaps instance:
google.maps.* objects:The supported events depends of the scope (i.e. a google.maps.Map object supports the projection_changed event, but a google.maps.Marker doesn't).
GMaps instances:According to the loaded modules, a new group of events can be supported (i.e. the gmaps.markers module supports marker_added and marker_removed events). For GMaps instances you can omit the scope argument, since always will be the GMaps instance itself.
You can check the supported events reading the GMaps.customEvents property.
off(eventName, scope)Remove all the listeners for the eventName. The scope can be any google.maps.* object that supports events, or a GMaps instance.
trigger(eventName, scope, object)Triggers all the handler functions attached to a eventName inside a scope. The scope can be any google.maps.* object that supports events, or a GMaps instance:
GMaps instances:For GMaps instances you can omit the scope argument, since always will be the GMaps instance itself. For custom events (defined in another gmaps.js module), you can pass an object (i.e. for the marker_added event, you can pass the recently added marker).
For pre 0.5.0 versions, check gmaps.js changelog
MIT License. Copyright 2015 Gustavo Leon. http://github.com/hpneo
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
FAQs
gmaps.js module to manage native and custom events
We found that gmaps.events demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
In this segment of the Risky Business podcast, Feross Aboukhadijeh and Patrick Gray discuss the challenges of tracking malware discovered in open source softare.
Research
Security News
A threat actor's playbook for exploiting the npm ecosystem was exposed on the dark web, detailing how to build a blockchain-powered botnet.
Security News
NVD’s backlog surpasses 20,000 CVEs as analysis slows and NIST announces new system updates to address ongoing delays.