Olestas wrote:It's not JNF fault. Its wme fault. Don't use Q/W for now.

Well it is and it isn't. There's a function JNF uses that's still in WME to toggle the state of a particular turn, however it apparently doesn't work correctly since the Turn Graph changes.

I've not had the time to figure out how to actually manipulate turns using the new Turn Graph functions and they're poorly documented in Waze's post about them.

Version 0.1.7
Chrome Webstore
2017-03-23: Reworked code so doesn't pollute global vars, updated to use SetTurn, jQuery based Google Place ID linkification instead of modifying WME code.

Version 0.1.8
Chrome Webstore
2017-07-25: Reworked GPID linking.

Version 0.1.9
Chrome Webstore
2017-08-01: Reworked GPID linking again in reaction to new Beta+Prod.

Version 0.2.0
Chrome Webstore
2017-08-09: Fixed loading issues.

Version 0.2.1
Chrome Webstore
2017-08-16: Modified @include preventing loading.

Odd it didn't publish, was still sitting in drafts for some reason.

Guess I forgot to update this with the last two pushes. Everything seems to work in production and beta.

rottielover wrote:Did the new version of the editor break this script? I can't seem to get it working for some reason (Chrome)

I haven't had any problems with it.


Sent from my iPhone using Tapatalk

rottielover wrote:Hmm. I'll do some more testing. When I have JNF active, saves take forever. When I disable it, it saves quickly. Maybe one of my other scripts is interfering.


Sent from my iPhone using Tapatalk

Now you got me thinking about it. Thought the slow saving was from the URs'. Seems if I edit, it's fine. Close a UR and edit, it locks up. I'll have to give a try with JNF off.