AlanOfTheBerg wrote:

bedo2991 wrote:Wouldn't it be safer to use another key instead of Q???

Today I accidentally found out I was restricting all turns in a roundabout instead of fixing its nodes. (Running JNF on Tampermonkey on Chrome, LMDE). Now I'm running it natively and doesn't seem to always work (the turns are not denied but the nodes aren't fixed).

Why safer? JNF doesn't make any changes to turn restrictions and only fixes problems.

I have found if you hit q too fast it will restrict all turns. I've found myself doing it several times, now I make sure I wait a second after selecting a node to hit q.

I saw on the Wiki Community Plugins, Extensions and Tools that this script would or could work with FireFox. I went to install it from Userscrpts. When loading WME I receive this error: WME Junction Node Fixer has failed to load due to API check: WCSAVE.controller" So for those who have gotten this to work on FireFox how have you done it? I've tried on FireFox Nightly with no success, big surprise. Any help or update to the script that would make it compatible with FireFox?

It seems to be steady as of this morning. It automatically is disabled in your Chrome extensions though and needs to be re-enabled. Why the permissions to *docs.google.com / *editor-beta.waze.com /* spreadsheets.google.com / * waze.com

I'm not concerned that it's stealing information, I'm assuming it's gathering segment information?

Thanks for the hard work to get it back up and running.

Can someone point me to the page that explains how to use this tool? From what I have read in this forum, it uses some of the existing shortcut keys as detailed in the Map Editing Quick-start Guide. It would be nice if the tool "Makes Dead Ends two-ways" & the "Terminates Dead Ends" on all of the segments in the screen (or selected segments, in conjunction with the WME Add-Ons.

I have it installed in Chrome as an extension, like the Highlights and WME Add-ons 0.41 but don't see any tab for JNF.

Thanks.

bgodette wrote: Checks WME's API to make sure used objects and functions exist and are the correct type. This works as long as function argument order doesn't change. Next step is to regex match on function contents to confirm arg order.[/color]

Saves the state of WME's ShowAllTurns, ShowTurns and Full-screen mode across F5/Permalink.
Forces data model reload after successful save.

This overloads the 'q' (disallowAllTurns) hotkey action to preserve existing turn restrictions.

• Fixes any self and reverse connectivity issues
• Fixes closed loop roads
• Terminates dead-ends
• Makes dead-ends two-way (only if both ends of the segment are visible)
• Sets the Type of a roundabouts using lowest of two highest rule and sets country/state if needed
• For UK sets Type of roundabouts using highest type excluding Freeway rule.
• Does a traditional 'qw' (clears reverse connectivity, and locks turns)
• Causes the turn arrows to refresh (the side effect of 's' but without the shifting).

Since you end up with the same turns restricted, that means you need to press 'w' if you really want all turns allowed. This is why it overloads 'q' instead of 'w'. Ultimately this will be a separate hotkey that's editable through WME's '?' interface.

If the main site is down, go to the mirror site:
http://userscripts-mirror.org/scripts/show/144939

olestas wrote:Actually most segments "should" have a u-turn... you can do this on most roads and junctions.
And highlights just informs about it... but this script by default removes u-turn.

I tend to disagree. A lot of segments and junctions will be mapped where road marking restrictions forbids legal passing, never mind u turns. You tend to forget that every segment junction does not really terminate where there is an intersection and I would guess many of them are in places where visibly of oncoming traffic is not taken into account.
Just take a connection between 2 adjacent segments on a 4 lane major highway mapped as a single lane as an example. Should that have u turns enabled by default? I think not.

The last thing a stupid driver needs is an app that tells him /her where to 'legally' make that u turn.

Sent from my HTC Sensation Z710e using Tapatalk 2

RodNav wrote:We have enough of those in South Africa, don't we?

No intention to hijack the thread, but I think it's a worldwide epidemic. If someone can get stuck in the middle of Oz or drive off a pier simply 'cos the SatNav said so, just imagine the spectacular u turns that will follow.

same here since last night in chrome and ff

Sent from Motarola Razr i using Tapatalk HD

I used to rely heavily on JNF before, not least the "q" shortcut to magically fixz 99% of junctions. I can't get it to work now and the comments in the thread indicate that it stopped working a while back. Is that still the case?

Ah, thanks.

I could not find anything about it in Toolbox, is it removed/hidden while it is not working or is it there but not working; if it's there, what should I be looking for?