Custom stop markers

3 posts / 0 new
Last post
kwinterton
Custom stop markers

So I just noticed today that a bunch of our custom stop markers are no longer working.  Looking through the documentation I noticed that there was a change to how the override for RouteLayer works.  Before we were overriding "createStopMarker" but now for some inexplicable reason it is necessary to override "createStartMarker" and "createEndMarker"?  We're already provided with a stop number, I can easily figure out which is the start and the end using that if necessary, but now instead I have to triplicate any code using this feature.

Is there an overarcing method I could replace as a way to create ALL of the stop markers? If not I would suggest adding additional arguments to the "createStopMarker" method to indicate a stop is the start or end rather than adding completely new methods


kwinterton
Another suggestion, why not

Another suggestion, why not have the default "createStartMarker" simply call "createStopMarker(loc, 1);"  So that if you override createStopMarker it'll call into your new override, but it also allows a user the ability to override createStartMarker if that's what the user wishes.


MQBrianCoakley
There are two new methods
There are two new methods that need to be overwritten in v2.1 for start and end markers - as mentioned above. Stop markers only effect middle markers now. You can use v2.0 rather than v2.s to stay with that version.