OlavoAG wrote:Hi there!

Is there any other source of download since Userscripts.org has not been working lately?
Thanx

If you are using Google Chrome Browser you can get it through the Chrome Web Store. It will then also update automatically when a version is published.

BUG report *2

1. This script is now conflicting with Toolbox, when both are running, I've isolated it to this script. The Fancy PL links to PM the last editor or creator of a segment in the left pane do not show. The link to display the list of area manager which should display below the segment history info also doesn't show.
2. When this script is running (with TB I haven't tested it without TB) there is a vertical scroll bar added to the map frame which allows a scroll of about 1/4 inch more of the screen (on a 720p screen in chrome)

If you need more data please tell me what you are looking for to debug if you are not able to reproduce.

qwaletee wrote:PZ, on bug #2, for some reason lately TB's minimap sometimes drops below the visible frame. Even if it is hidden, this causes Chrome to think that it needs to allow you to scroll down.

Just enable the minimap and drag it up. I think it only happened once, during a recent update, so you can do this once and forget about it.

This bug2 is not the TB minimap bug, I don't get it with just TB, only when route chcker is also enabled. I'm aware of the mini map bug, and I even tested with mini map enabled and in middle of screen.

Sent using Tapatalk for Android 4.4.2

Another slightly more time consuming but accurate workaround is to create a new short helper segment, so you can choose where the mid point will be that is passed to livemap. Ensure that midpoint is nearest to the segment you want to start/end on. You can manipulate this segment for the desired result. You don't need to worry about the segment being connected to anything or interfering with results, since the results are drawn strictly from the segments in the live map.

Sent using Tapatalk for Android 4.4.2

russblau wrote:

Timbones wrote:0th exit is an error in the map - you must not have two exits from the same node on the roundabout.

I'll tell DDOT that they made an error designing Dupont Circle. [emoji38] Which I'm sure they will enter in volume 37 of their compendium of poorly designed streets.

Or you could fix it by having a single no name segment exit that node, and then fork into the two roads. So the RA sees it as one numbered exit, and the prompt will still carry the same names do to the no name segment properties.

Sent using Tapatalk for Android

When choosing to select the route segments, you lose the tab from the left and have to re-select the original two segments to get it back.

is it technically feasible to add the ability to route based on immediate edits? or is the routing engine only available for edits that have been committed to the live map? if it's technically feasible that would be a great feature to have -- so you can test your edits without having to wait up to 24hrs or more. if not, perhaps that's something we can put on our Waze wish list...

MK2312 wrote:Does your script really needs to have access to all URLs / history?

+1

I just seconded this for WME Toolbox as well. I like that people are making noise about this - Chrome extensions should be properly scoped. thank you!

Szata76 wrote:The Shift + R shortcut doesn't work in WME if the RT extension is turned on. I think this is the reason.
Shift + R | Toggle [missing "en.layers.name.route_checker" translation]

I also see that problem. Tim, could you change it to Control-R? I don't think that's assigned. Or offer us an option to choose the hotkey and/or toggle hotkey latch?

Mike-1323 wrote:

qwaletee wrote:

Szata76 wrote:The Shift + R shortcut doesn't work in WME if the RT extension is turned on. I think this is the reason.
Shift + R | Toggle [missing "en.layers.name.route_checker" translation]

I also see that problem. Tim, could you change it to Control-R? I don't think that's assigned. Or offer us an option to choose the hotkey and/or toggle hotkey latch?

Ctl-r triggers a page reload in Chrome and FF so that's not a good one to use.

Doh! I should have known that. Been bitten by it in a couple of designs.

I just discovered the editable keystrokes. I just wish it warned you when you are overwriting an existing key assignment.