Added more support for projected points

[amjaliks]

Added method setProjectedContraintsSW:NE: to RMMapView class.
Added method addMarker:atProjectedPoint: to RMMarkerManager class.
Added function RMProjectedPointEqualToProjectedPoint.
Added property centerProjectedPoint to RMMapContents class.

P.S. It isn't a refactoring, it is an addition.

[hjon]

I actually tried setProjectedContraintsSW:NE: some time ago and it seemed that it didn't produce the same results as setConstraintsSW:NE: (when using coordinates and projected coordinates that should have been in the same location). I don't think this is your fault, as what you did looks fine and I would have done the same.

Have you tested this successfully? It's certainly possible that I messed up when I tested it.

[amjaliks]

I work on project where I operate with projected points (because, the source have some specific projection). This why I have added setProjectedContraintsSW:NE:. And, of course, I use in my project. It works perfectly.

setProjectedContraintsSW:NE: does the same as setConstraintsSW:NE: does. If you look at an old implementation of setConstraintsSW:NE: and a new setProjectedContraintsSW:NE:, you would see the only difference, that old method calculates projected points, while a new method them directly to ivars.

[incanus]

Why does this pull request & this commit make -[RMMarkerManager addMarker:AtLatLong:] deprecated if it's "just an addition"? That's a particularly useful method and it goes towards making route-me more MapKit-like in that it deals directly with latitude & longitude.

If desired, I can create a pull request with a patch to bring this back out of deprecated-land.