Hm, am I correct in assuming that if I add a theme to the elevation shortcode, that takes precedence over any value I add to the color= om the leaflet-gpx shortcode?
I have this
[leaflet-gpx src=”https://domain.se/wp-content/uploads/sparet1.GPX” color=#f15a22] *This color is the track’s orange identification color on signs in the terrain and on map materials.*
[elevation gpx=”https://domain.se/wp-content/uploads/sparet2.GPX” theme=lime]
I can actually see the orange track before extensions adds a black line with a white shadow
I see this in dev console.
.elevation-polyline {
filter: drop-shadow(1px 1px 0 #FFF) drop-shadow(-1px -1px 0 #FFF) drop-shadow(1px -1px 0 #FFF) drop-shadow(-1px 1px 0 #FFF);
}
And the source code for the track.
<path class="elevation-polyline lime leaflet-interactive" <strong>stroke="#000</strong>" stroke-opacity="0.75" stroke-width="3" stroke-linecap="round" stroke-linejoin="round" fill="none" d="M525 310L508 305L497 299L494 </path>
So I end up with a track that blinks orange and goes to a black track with white shadows and a green elevation graph. ?? Is there a way to tell the plugin to stop messing with the gpx-track if it got a color= option?
-
This reply was modified 2 years, 11 months ago by
Argentum.
-
This reply was modified 2 years, 11 months ago by
Argentum.
-
This reply was modified 2 years, 11 months ago by
Argentum.