[Script] WME Color Highlights - 2.33 Sept 2020

[GooberKing]

When I open editor with places turned on, this thing happens after I click on any place.

I fixed an issue that was occurring on Firefox (v2.2). Let me know if that fixes it.

As for Chrome, I still can't see any problems. What errors do you see in the Developer console?

Not sure what you fixed, but it looks like the HN Panel is now working in Firefox as well. Thanks!

[goodolsen]

Seems like most add-ons that worked before the update to WME need to have their own updates.

[HandofMadness]

Presumably a good portion of the house numbers on the older streets are set / were imported with the help of the geocoding sources. Undoubtedly they need to be tweaked - prompted by UR's.

Why, they aren't currently used by Waze search? The address layer is just there to divert you from working on stuff that actually affects routing, or giving you something to do if there's nothing left in your area. Typically, when Waze announces a new functionality is just around the corner, its 12-24 months out. Since they've yet to make any announcement that they plan on using editor entered addresses "just around the corner", I think its safe to assume we're several years out from them serving any purpose.

/Why yes, I am cynical.

[HandofMadness]

Any updated version for the new beta editor URL?

[HandofMadness]

Any updated version for the new beta editor URL?

You can update it yourself. Right at the top. Pretty easy.

I know I can unpack the CRX file using 7-Zip. Once I change the URL's in the script, how do I repack it so Chrome will let me install it?

[HandofMadness]

I'm running 1.6.7 and for some reason I'm not getting any of the AM level functions, despite being a CM.

[HandofMadness]

* Updated Chrome version (v1.7.4) so that it will work with non-English languages.

Where do I get 1.7.4? Latest version I'm seeing in the link from the first post is 1.7.1.

[Harmonious4]

I have written an update to this script so that the routing preference highlight shows the colour of the routing road type, rather than a cyan highlight for all road types. Where should I be submitting my code?

[Harmonious4]

I have also been using a modified version of the script, which changes the colour of the routing preference highlight based on the routing road type rather than always cyan:

Code: Select all

      //newColor = "#0ff";
      switch (attributes.routingRoadType) {
        case 1: // St
          newColor = "#ffffeb";
          break;
        case 2: // PS
          newColor = "#f0ea58";
          break;
        case 3: // FW
          newColor = "#c577d2";
          break;
        case 6: // MH
          newColor = "#45b8d1";
          break;
        case 7: // mH
          newColor = "#69bf88";
      }


Is there any interest in adding this to the script?

[hawkeygoal]

I haven't deduced a specific cause of the malady, but I'm finding that I'm getting locked in a shaded screen after some edits, particularly if end point nodes have changed in Chrome. I noticed a looping error in the console and identified the faulting instruction was in Color Highlights, specifically ln 736.

VM80754:736 Uncaught TypeError: Cannot read property 'attributes' of undefined

This might be associated with something else I've been noticing (possibly unrelated) that pops up associated with wLib:

VM172751:2 module Waze/Presenter/FeatureEditor/Segment not found

Following this error I'll find seveal 500 level responses from http://www.waze.com. However, I'm not nearly as adept at script writing as I would need to be to do a proper RCA on all this. Just seems something is possibly amiss.