Blayter.com

cf_googleMap v.1.3

There are a lot of items that went into the 1.3 release. I have been slammed at work and some remodeling at home so it has been hard to find time to wrap up this release. Once again I must thank Jeff Gladnick for some invaluable feedback and most importantly a base code for a better geocoding engine.

  1. Changed the logic for the mainpoint attribute so it can be overwritten when a false value is passed.
  2. Added documentation for to the mainpoint and how it defaults to true when there is 1 point on a map
  3. Removed the default 1px blue border around the DIV container for the map and replaced it with a style attribute for the googlemap tag.
  4. Added the show attribute to the cf_googleMapPoint tag
  5. Added the GM_clearMap() JavaScript function
  6. Changed the max characters for the driving directions from 40 to 255
  7. Added example for using the geo.cfc Geocode
  8. Renamed the Geocode function to GeocodeUS
  9. Added a new Geocode function based off of code provided by Jeff Gladnick. This should provide a much more accurate geocoding including international addresses.
  10. Added callJavaScript attribute to the cf_googleMapPoing tag

You can view the details of the changes on the project page or download it on RIA Forge

Comments
Hi John,

I love the tag, thanks for putting this together.

The "show" attribute doesn't seem to be functioning, however.

I also cannot seem to interact with the map (zoom, etc) until after the map point has been clicked on.

I'm getting this behavior on a mac in both firefox and safari.
# Posted By Bryan | 1/29/07 11:22 AM
Great work, thanks for it!
When I play around with your examples, in IE (version 6) a Javascript error will show up (object is not support, line 300). Have you got any idea how to fix this behaviour?
# Posted By Dirk | 2/5/07 12:10 AM
Dirk,

I have not seen this issue before today so I am not sure how to fix it. I will take a look at the JavaScript later on to see if there is a solution to the problem.

Thanks

John
# Posted By John Blayter | 2/5/07 8:49 AM
Dirk,

This appears to be an JavaScript issue with the latest MAPS API that Google releases. I am going through my code to see if by a certain way that I am using the API is causing this issue.

Thanks,

John
# Posted By John Blayter | 2/7/07 5:45 AM
Looks like I spoke too soon. I found an issue in my code that was causing the JavaScript from Google to error. I took what I had done on 1.4 and the bug fix and included it as the 1.3.1 build. Download it and let me know if it resolves your issue.
# Posted By John Blayter | 2/7/07 6:05 AM
John,

thanks a lot for your bugfix!! I will test it tomorrow, but your examples look really good. No script-errors anymore :-)


Many regards, Dirk
# Posted By Dirk | 2/10/07 2:22 PM