PR merged Quite painless operation that could be done while queuing to pay for a 21mm socket (for tightening wheel bolts)

Oh, and if we'd really want to utilize GitHub, I could set up a separate "development" branch that could then be used for testing new stuff, before merging into master. The dev branch could then be used by brave testers who don't mind occasional problems or something. Master would then be considered "release quality"... just some thoughts.

qwaletee wrote:If you place the instruction indicator centered on a line, then you can rotate the text to be perpendicular to the line, and stack two instructions. You would end up with three "rows" within your container:

• Line closest to junction - directions from "this" segment toward the "other segment" coming out of the junction.
• Line containing the turn angle.
• Line furthest from junction - directions from the "other segment" to this segment

Hmm.. Not entirely sure I'm able to visualize this correctly in my head
3 lines inside the marker is probably going to make the markers biggish or the text really small..

I wonder if is possible to have multicolored markers =D As in, split in half with matching color code somehow matching the direction.. Might need some deeper insight into how OpenLayers actually work though.

New version (1.9.0) is out Anomalies and meltdowns may happen, so please report any findings that our testing didn't catch yet (either here on the forum or as a GH issue).

Big thanks to FZ69617 and wlodek76 for code contributions and everyone else for ideas.

Edit: typos

qwaletee wrote:When selecting a junction (not a segment), do you want to use the absolute/departure setting, or always absolute?

Can't really calculate an "out"-angle without a defined "in"-angle

EWK333 wrote:Hi, is there a way for this script to not automatically be active when WME loads?

Thanks

Or hide the corresponding map layer?

EWK333 wrote:

PesachZ wrote:No, I uncheck it in the drop down layers menu, then it is checked again every time WME is reloaded. I just click on the 'Edit The Map' link from Live Map, so the only parameters are Lon, Lat, and Zoom

Probably something to do with the fact that the layer is added only after WME is loaded already.. Maybe would be possible to store a value once the layer is shown/hidden, and then use the stored value to programmatically hide the layer if desired..

I do recall the layer visibility was working correctly at some point though, as I was wondering why the script would not load (turned out is was simply not checked) [emoji12]

Olestas wrote:Can you please publish your latest version script?

sure Unfortunately it will have to wait until tomorrow..

Extensions and the greasyfork version will probably be updated tomorrow once I've verifoed they all work as intended

milkboy wrote:Extensions and the greasyfork version will probably be updated tomorrow once I've verifoed they all work as intended

Addons tested and uploaded to Chrome webstore and addons.mozilla.org (may take a while until they become available). The Greasy Fork site seems a bit unreliable, but I guess the most recent version was synced there also.

For Firefox addon users: the addon is now marked as supporting the new multiprocess architecture of Firefox. It works nicely for me, but ymmv. Oh, and I added "private-browsing" permission also, so it should now work in private mode also (only settings are stored anyway, no browsing history or other data).