why does update call onMapMove?

[jfirebaugh]

If there's no parseable hash (e.g., if there's no hash at all), update calls onMapMove. This seems counterintuitive: I'd expect update to work in strictly the opposite direction from onMapMove. That is, onMapMove is strictly for map -> hash updates, so I'd expect update to be strictly for hash -> map updates.

[mlevans]

Hi John,

Sorry for the delay.

If there's no parseable hash, the idea is to call onMapMove to reset/update the hash to a sane value — where the initial map view matches the hash. Would you implement it differently?