Documentation claims only this:
/** How long it takes the marker to fade in and out when visibility changes. */
@property (nonatomic, assign) CGFloat fadeTime;
Does this CGFloat value represent seconds? milliseconds? No matter what value I supply:
[marker setFadeTime:3000.0f]; // assume milliseconds
marker.fadeTime = 3.0f; // assume seconds
It doesn't seem to change the behavior. Any help is appreciated.
(Apologies - not enough reputation points yet to create a
citymaps tag - any 1500+ members, please feel free to assist!)
Best How To :
I am a developer at Citymaps. Thanks for putting up with our, rather bare, documentation. Looking at the docs made me realize that we're missing a few key properties on markers, both on iOS and android (oops).
To answer your question, fadeTime will adjust the speed that the marker fades in or out by when its visibility changes. Right now, visibility will only be changed through the collision detection feature of CEMarkerGroup. One of those missing properties I mentioned was a 'hidden' property for iOS, or a 'visibility' property on Android, similar to their respective View class.
I've updated our docs a bit to answer the question of what unit this value is. We try to follow the convention of the platform. For iOS, this value is in seconds. On Android, this value is in milliseconds.