xteejx wrote:I'm not on your server mate. Assume it's probably the same though, or perhaps MPs are run manually these days. Just so strange that there's been an influx of users yet no detected issues...
Sent from my GT-I9100P using Tapatalk 2
CrackedLCD wrote:Timbones wrote:And it's not even specific to the JNF script - any editor can use QW on every junction node they see with red arrows, blindly allowing all turns without adding value to the map and destroying any information that may have been there.
Displaying 'measles' to every road just presented another excuse to 'fix' junctions that didn't need fixing.
This line of thinking may be appropriate for where you live, but in my part of the US, minor roads on Waze are often very heavily travelled despite not qualifying for primary or minor/major highway status. And in suburban areas, we don't have one way streets or, for that matter, much in the way of turn restrictions, so blindly allowing turns and fixing revcons are actually not that harmful for 99% of the area that I cover.
Timbones wrote: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 wrote:skbun wrote: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.
Users browsing this forum: carloslaso