-
…ing. no tests written to these yet though.
-
- (id) initWithCGImage: (CGImageRef) image - (id) initWithCGImage: (CGImageRef) image anchorPoint: (CGPoint) _anchorPoint - (void) replaceImage:(CGImageRef)image anchorPoint:(CGPoint)_anchorPoint cleanup: - (id) initWithUIImage: (UIImage*) image add: - (void) replaceUIImage: (UIImage*) image anchorPoint is left to CALayer default (0.5,0.5) User can override with: marker.anchorPoint = CGPointMake(?,?);
-
… use -truescaleDenominator. Memory warning responses are now correct.
-
…ethod to RMMapContents. Added documentation.
-
…eiveMemoryWarningNotification and cascaded didReceiveMemoryWarning calls to its components.
-
… to memory warning handlers. Made Doxygen target open completed doc tree after build.
-
…ings. Tweaked Doxygen configuration.
-
leave RMTileHash as it was for use by the RMTileImage NSObject
-
rewrite RMTileHash to avoid collisions since the Caches don't check or handle them. Should handle any map up to: 256 zoom levels (2^28)-1 x values (2^28)-1 y values If you have a map outside those bounds, I want to see it as it must be pretty cool.
-
Ultimately, RMMemoryCache and RMDatabaseCache will take action if present
-
Add [overlay correctPositionOfAllSublayers] to setZoom/setScale to fix issue w/ wandering markers