[Script] Highlights for Segments & Landmarks - v1.5 Nov 16

[Timbones]

I regret to report a possible problem.

I installed v1.4 last night and have been working on a basemapped area. I began to notice that I wasn't seeing any selfcons (red highlights) despite situations where I would expect them. I downgraded to v1.3 and found one almost immediately where v1.4 didn't.

Thanks Iain, I'll take a look...

via mobile

[Timbones]

However, I assume that in amongst the bugfixes, was one that "fixed" erroneously named roundabouts not to show as yellow/orange, which, as was briefly discussed in the thread recently, was very handy - particularly in my neck of the woods!

I'm considering adding a separate highlight for roundabouts which are named or two-way, but haven't quite settled on how to display it...

[Timbones]

I installed v1.4 last night and have been working on a basemapped area. I began to notice that I wasn't seeing any selfcons (red highlights) despite situations where I would expect them. I downgraded to v1.3 and found one almost immediately where v1.4 didn't.

Well spotted! I knew I should have kept this in beta testing for longer...

Anyway, this issue fixed in v1.4.1

[Timbones]

Still no highlights on those nodes I quoted before.

Looks like a bug specific to Firefox. Works fine in Chrome. I'll see what I can do...

[Timbones]

Okay, I really think I've got it now. Tested in Firefox, Chrome and Tampermonkey.

v1.4.2 - http://userscripts.org/scripts/show/141050

[Timbones]

I don't know what version I'm running, but if I see 30 Oct 2012 in the title, I'll know I have to upgrade.

I'll try, but there's not much room in the title for anything else.

The version is shown at the top of the highlight options, and the title links directly to the page on userscripts. It shouldn't take much effort to manually check for a new version now and then.

I did consider adding an automatic check, but it seems a little late in the development life cycle. I'm not expecting many updates from this point on...

(my other script hasn't changed since March)

via mobile

[Timbones]

Rename it to wme-highlights.user.js and try again. Probably worth removing old versions too.

via mobile

[Timbones]

+1 on the suggestion from skbun about making it possible to see all problems in an area using a colour coding for all segments that have issues.

This was how it worked in an earlier version but it showed an aweful lot of problems, most of which don't actually need fixing. I felt that showing all nodes with soft-turns would encourage editors to QW all of them, which adds little value to the map and increases the chance of turns being set incorrectly. Therefore, I took the decision to only show them for one node/segment at a time, for when a particular routing issue needs to be diagnosed.

I saw a post earlier in thread about not seeing the segment/junction warning highlights. The properties toolbox says "x soft turns, y u-turns" etc., but the segments don't highlight.

This was fixed in v1.4.2. Do you have the latest?

If I touch any given segment, and then click 'Save' in WME, any segment which I had changed comes up with a wacky speed result. It doesn't matter whether I have any node (or the node in question) highlighted when I do click save; this result persists until I reload the page.

This is a known bug in the WME code, for which I may include a fix for in future versions.
Workaround for now is to reload the editor, or ignore the crazy speeds.

[Timbones]

I'm running the exact same version of Chrome, also on Windows 7. Works okay for me.

Can you post a permalink that shows this problem?

[Timbones]

Did you enable the advanced option [ ] Turn Warnings for Selected Nodes?