Hmm.. wha?
Can you patch linking to display full name ?

bgodette wrote:

Olestas wrote:Hmm.. wha?
Can you patch linking to display full name ?

Click the link? There's only so much room.

I mean a popup. Don't want to open google maps for each link.

bgodette wrote:

Olestas wrote:

bgodette wrote:Click the link? There's only so much room.

I mean a popup. Don't want to open google maps for each link.

A mouse-over bubble for the link or the entry field?

Yeah, over Entry field, when there is something linked.. to see full length. I understood that some browsers show this popup by themselves. But chrome does not.

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

CTGreybeard wrote:I'm running 0.0.7.6 under Chrome 27.0.1453.110 and a strange thing has just started happening. When I highlight a segment the turns are all "grayed out" and can't be changed. I can click on a node and change All Allowed or All Disallowed but I can't change individual arrows or u-turns. If I disable the extension and reload the page then I can change the arrows individually.

The same version running under Firefox doesn't show the same problem.

I know it was fine earlier today under Chrome. Maybe I'm just going nuts.

Did you by chance accidentally press the A key on your keyboard? That shortcut toggles on a mode where the turn restriction arrows are dimmed and can't be clicked, so that you can make fine adjustments to things like geometry nodes which are so close to the arrows that they would otherwise get in the way. Just press A again to toggle it back to normal. Forgive me if you know and have tried this.

EDIT: I just realized that my comment doesn't apply to your situation, because your problem disappears if you disable the extension. I am wondering, though, if something in JNF is triggering the 'A' mode I mentioned above. Does pressing A by any chance make the arrows available while JNF is enabled?

sketch wrote: I get the error sometimes when already logged in, actually. I'm not sure what the problem is, but I believe it started happening only after I installed the Chrome Web Store version.

I've had the problem before the Chrome Web Store version was released, but it has presented itself more frequently since then.

Login status does not make a difference in my case. I never really log out, and when WME loads, following this API check message, I get the user greeting, and current points status, et cetera, confirming that I'm indeed logged in.

It has something to do with the latest version of Chrome (27.0.1453.93). Toolbox has exactly the same issue.

You can download a working version for Chrome here:
www.wazeteam.com/chrome/WME_Junction_Node_Fixer.crx

BellHouse wrote:To open one, there is a small one time fee

Wrong: you can publish up to 20 extensions for free. The rest is true

If bgodette agrees, I can publish a chrome extension on the store