gmap 6.x-1.1-rc1

Changes since DRUPAL-6--1-0:

• Brown paper bag fix. I broke hyphenated mapids back in September and it took me this long to notice.
• Keep track of a per-map storage handler variable. It can be accessed if needed by adding a second parameter to the callback function.
• Roll back last commit. I just realized it isn't actually needed.
• Document extramarkerevents and the new clickableshapes behavior flags.
  Add shape clickability.
• #350408 by pillarsdotnet: Selecting "Regenerate marker cache" does not reliably clear and rebuild the marker cache.
  Changes:
  gmap_regenerate_markers()

  * Pass TRUE to the gmap_get_icondata() function
  * Pass TRUE to the gmap_set_marker_titles() function

  gmap_set_marker_titles()

  * Simplify and correct the caching logic

  gmap_flush_caches()

  * Add an implementation of hook_flush_caches to ensure that clicking on the "Clear cached data" button from the /admin/settings/performance page also rebuilds the marker cache.

• Testing hg workflow.
• Add a forgotten ensure_table() call and fix the aliases used when adding the location fields.
  As a side effect, this means that using a location_cck relationship will now do the right thing for a gmap view.
• Add the ability to base gmap views off of arbitrary fields. Also add a way to specify the marker using a field.
• #351912 by mleicester: Force gmap to properly respect a custom marker path.
• Fix several block issues.
  * Allow multiple locations for users and nodes.
  * Fix marker titles and give them sane values.
  * Add offset to make markers with multiple images work as expected.
  * Rewrite gmap_location_author_block_view() to work similar to gmap_location_block_view().
  * Remove hardcoded 'gmap_location_authorblock' mapid to match the behavior of the node block. (Reassign it in the macro if you need it.)
• Diff minimization
• #353098, reported by surge_martin: Use correct criteria for determining non-blocked users.
• gmap_parse_macro will assign ids as needed, no need to manually assign one.
• #141747: Fix user page query to let multiple locations for users work.
• add a class around map bubble contents. you can now set width and height on .gmap-popup in your css and map bubbles will grow to fit it.
• look in correct js variable for nomousezoom setting
• #364573 by Pasqualle: Fix invalid HTML in help file.
• Rewrite pieces of icon.js more defensively to prevent prototype bugs and type errors and so forth.
• gmap_taxonomy fixes:
  * Clarify what the first option for the marker does.
  * Fix unsetting a marker deliberately
  * Fix several bugs with updating marker associations after changing a term.
  * Fix SQL error when setting a marker on existing terms.
  * Add function to recompute markers after changing a term.
• @bec: This was causing warnings on pages with markerless maps (like the settings page.)
• #349318, reported by jeeves: Fix empty map being displayed for 0.00,0.00 locations.
• Remove the gmap_geocode variable, it doesn't do anything anymore.
• Fix variable usage bug. It hasn't caused problems because the backwards compatibility variables are still being used as a fallback.
• #128272: Finish writing the gmap_location uninstall hook.
  Also, I changed some % to %%. Although this wasn't a problem in practice, using a single % means relying on internal behavior of db_query.
• #367547 by ssherrie: Add user role markers capability to GMap views.
• Fix #365384 by attempting to explain the variable better.
• JSLint whitespace
• Fix access to _handlers and _maps, finally.
• Forward port missing changes from 1.1.2.39 (7/24/2008 11:13 PM):
  Make getMap a bit more user friendly by allowing passing widget ids.
• JSLint runs and misc. javascript cleanup.
• Remove cargo cult hack that has apparently been obsolete since GMap started using the 2.x api.
  http://groups.google.com/group/Google-Maps-API/msg/33df59945c139afe?dmod...
• Trim unneeded line from gmap_menu().
• Change marker chooser to add an empty "Default" option if the element is not #required.
• Add support for ClusterMarker and MarkerManager (without the G) marker managers.

  Fix #155104 by Scott Falconer: Add "Zoom to cluster area" support.

  Allow falling back to the default Clusterer marker if desired.

  Allow entering larger numbers in some marker manager settings.

  Allow choosing between the original and the new "zoom to marker area" behavior on Clusterer.