Page 12 of 82

Re: [Script] WME Color Highlights - 1.91 July 2014

PostPosted: Mon Sep 01, 2014 4:00 pm
by ct13
SuperDave1426 wrote:
Taco909 wrote:I'm not sure that Validator is catching Revcons.

Ok, I'm putting on my stupid hat now. [ img ] :D

But what the heck is a "Revcon?" I've seen the term bandied about, but I just can't figure out the meaning (beyond a really vague idea) from seeing it used. So, I give up. :lol: What does the term mean, at least within the context of Waze?

Basically they are unneeded turns that have been allowed on one way streets. It usually happens when a two way street is converted to a one way, or when you switch directions on a one way street.
(I posted a link before Dave!)

Re: [Script] WME Color Highlights - 1.81 Mar 2014

PostPosted: Thu Sep 10, 2015 6:46 pm
by ct13
vince1612 wrote:Hey all,

A suggestion which -I think- was not talked about before -sorry in advance if I'm wrong-, I did look through the pages of this thread and didn't find anything.

Currently I use the "Recently Edited (Green)" highlight function a lot and the fact that you can filter by editors is great too !

My question/suggestion is would it be possible to have the option to highlight everyone's edits except your own by filtering them out.
AND/OR to highlight by editor rank (only highlight edits from lvl 1 users, or 1 and 2)

This would be useful to me for two reasons:

1. You could always leave the feature ON even when you work/edit the map as it would not highlight roads you need to see without the green highlight blocking your view of street names, currently I have to turn it off when it bothers me and not forget to turn it back on after I'm done.

2. As an AM who may want to review edits in my area to check for potential mistakes by new editors I would be able to quickly notice edits who were not made by me and not risk zooming on my own edits to check the zone.
  • -> If filter "everyone except me" the only problem might be that edits from higher ranked editors would also be highlighted, but not a big issue, would already be great.
  • -> If filter "by editor rank" it would be simply perfect to review recent edits by lower ranked users and be able to spot possible mistakes quicker. Then I can message the user to guide him to the Wiki's or help myself etc...

Currently without that option I can also sort of use this to check recent edits but I edit so much that often I zoom on places that were edited by me and loose some time.

uscwaller wrote:For the 'Filter By Editor' option, it would be nice if they were sorted by either rank or alphabetically

So I wrote a post to ask for feature additions to the "filter by editor" highlight and lo and behold others had most of my ideas first. :D

So in addition to bumping this to see if there were any plans to incorporate these features, I would also like to suggest having the ability to highlight multiple editors. Sometime, you run into an issue where there are a few editors that you would like to pay closer attention to; having the ability to highlight multiples, rather than switching between editors while panning the map, would make it much easier.

Regardless, great script that makes editing and managing much easier. Thanks!

Re: [Script] Highlights for Segments & Landmarks - v1.6 Feb

PostPosted: Tue Feb 26, 2013 11:29 pm
by cybernissart
Observed on Chrome. Don't know for FF.
It looks like there is a mistake between Toll and Locked features in 1.6 as:

- When selecting Lock, it displays locked segments with a Dash
[ img ]

- When selecting Toll, it displays toll segments with a Red
[ img ]

Re: [Script] WME Color Highlights - 2.9 JUL 2016

PostPosted: Thu Sep 15, 2016 12:03 pm
by cybernissart
WME Highlight v2.12 Filter by City broken since WME cityID stateID attributes were introduced 12/09 by Waze.
Following error returned at line 972 on Chrome.

VM12909:972 Uncaught TypeError: Cannot read property 'localeCompare' of undefined

Re: [Script] WME Color Highlights - 2.9 JUL 2016

PostPosted: Thu Sep 15, 2016 1:17 pm
by cybernissart
I could recover by modifying some part of the code as below.

Add new object definition at Line 941:
Code: Select all
   var cityname      = Waze.model.cities.objects[cid];
   var citystateid   = Waze.model.cities.objects[cid].attributes.stateID;
   var citycountryid = Waze.model.states.get(citystateid).countryID;

Change Line 943 by:
Code: Select all
      cityObjs.push({id: cid, name: cityname, state: citystateid, country: citycountryid});            

Not check yet other part of code, but other function seem to be ok.
Hope this would help if you need it to go on with your daily work.

Re: [Script] WME Color Highlights - 2.20 OCT 2016

PostPosted: Tue Oct 04, 2016 7:30 am
by cybernissart
Oops ! Just realized that I was still running an old version 2.9 of the script. Fortunately, the error introduced by the change in Waze model definition applied also to current.

Can you Tim perhaps change the Topic title to remove the "2.9 JUL 2016" reference ?
Your last Update to the thread was adjusted to "2.20" but only apply to your post, and still leave the topic to that previous version... Confusing for those relying on it to potentially followup and update.

Also, in order for script to automatically update, you may perhaps change the @namespace in top script ?
Code: Select all
// @namespace 
Code: Select all
// @namespace 

Re: [Script] WME Color Highlights - 2.23 Jul 2017

PostPosted: Mon Oct 16, 2017 10:09 am
by d2-mac
Please add segment highlighting by street names.

Re: Re: [Script] Highlights for Segments & Landmarks - v1.6

PostPosted: Tue Mar 05, 2013 9:03 pm
by Daknife
khaytsus wrote:
Timbones wrote:I'm afraid not. The script is deliberately coded to only show turn issues on major roads to encourage responsible editing.

Confused, why would showing on other streets be irresponsible? Only thing I could think of is it would possibly show too much information, distracting some editors?

I agree with this. Not every intersection in a subdivision may have issues, but many do, and it saves time if we don't have to click on every junction node to see if it needs a QW.

Also anyone else have issue with how it no longer shows your locked roads with any color? I usually have it set to show streets I've edited to be able to track my progress through areas, but I've noticed that if that is set it doesn't tint the roads I've locked at all, whereas it used to and I liked that feature.

Re: [Script] Highlights for Segments & Landmarks - v1.6 Feb

PostPosted: Tue Mar 05, 2013 9:05 pm
by Daknife
Most newbie editors that may make the mistake WeeeZer14 discussed don't know about the script.

Re: [Script] Colour Highlights for Segments - v1.6.2 Apr 201

PostPosted: Sun Jun 16, 2013 6:02 am
by Daknife
Or more accurately the last Chrome update disabled the old scripts by implementing a new script packaging format, as Alan noted there are links to the correctly packaged scripts that work fine.