On Oct 29, 12:28 pm, "pamela (Google Employee)" <[EMAIL PROTECTED]> wrote: > Honestly, we weren't aware that the loader change would have the effect of > disabling these symbols.
I don't know if you have heard of Jeremy Paxman, or heard him say "Ye- e-s", but I think that statement is rather surprising, I'm afraid. Loader tokens must be documented somewhere, so it should be possible to find what's likely to happen if one is changed. > That said, I wouldn't consider it a bug, since > these aren't a part of the v2 Maps API. > What would you suggest as the best way to document in the changelog? Just put an entry in the changelog: New loader v.234 (is there a version number? If not, just the date) - Loader token _mF[n] removed Effect: v1 map-type constants removed from v2. I appreciate that there isn't the "preview" mode for the loader code, but at least this way there is something official to point enquirers at. Not every change to the loader would need an entry, for example adding a new token to cater for new functionality which may or may not have made it to v2.x; but making a change to anything which is already there should be mentioned. Andrew --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to Google-Maps-API@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Maps-API?hl=en -~----------~----~----~----~------~----~------~--~---
