Page 205 of 236

Re: [Script] WME Validator 1.0.2 / 04.07.2014

PostPosted: Mon Aug 04, 2014 6:06 am
by SuperDave1426
Thanks for that, though I don't know if you can edit the native Chrome script that's been installed in that fashion. Does anyone know if the userscripts version works in Chrome under Tampermonkey?

What I'd really like to know is why on Earth this thing needs an expire date, of all things? I really don't see what useful purpose it serves....

Edit: Well, I went ahead and gave it a try. So far, it seems to function just fine in Chrome as a userscript being handled by Tampermonkey. Which means I could put in the modification suggested, and now it seems to be running again. Yay! :)

Re: [Script] WME Validator 1.0.3 / 04.08.2014

PostPosted: Mon Aug 04, 2014 4:09 pm
by SuperDave1426
I just fired up WME and got an update announcement for the Validator. Looks like he finally pushed out an update. :)

It would be nice if this update did not have an artificial, unneccessary expiration date in it.... :?

Since the userscripts version does seem to work under Tampermonkey in Chrome, I'm just going to keep using that so that if it does have another expire date, it will be easy to disable next time.

Re: [Script] WME Validator 1.0.3 / 04.08.2014

PostPosted: Wed Aug 06, 2014 2:05 am
by SuperDave1426
wlodek76 wrote:Maybe a better solution could be displaying some annoying popup window during start instead stopping the script from working. Let's say you need to go to vacations and there is a problem because upgrade needs to be placed manually on specified date.

[ img ]
Seriously.

Toolbox will pop up a message when you start it if there's a newer version available and the auto-update feature in the browser hasn't auto-updated it yet, letting you know that it's time to update. You can click on ok and happily continue to work with it, but it doesn't stop working just because there's a newer version.

If similar code could be added to Validator so that when the "expiration" date has passed and there actually isn't a new version online yet, at least that way people could continue working until the new version is available online to provide that update.

Just a thought.... :)

Re: [Script] WME Validator 1.0.3 / 04.08.2014

PostPosted: Fri Aug 22, 2014 4:45 pm
by SuperDave1426
I appreciate having it, too. I don't see that above field (Updated by) when I bring up the search tab.

Is it restricted to CMs & RCs?

Re: [Script] WME Validator 1.0.3 / 04.08.2014

PostPosted: Fri Aug 22, 2014 6:01 pm
by SuperDave1426
crazycaveman wrote:
SuperDave1426 wrote:I appreciate having it, too. I don't see that above field (Updated by) when I bring up the search tab.

Is it restricted to CMs & RCs?

It is restricted to CMs, as stated in the FAQ

New! Search for a specific username
Validator does support a search for a specific username. Click "search" tab and put a desired username(s) into the "Updated by" field.

For privacy reasons the feature is available for country managers only. Regular users and area managers have "Include only your edits" option instead.

Ok, thanks. I wonder if he can be persuaded to add State Managers, at least within the states they manage....

Re: [Script] WME Validator 1.0.3 / 04.08.2014

PostPosted: Fri Aug 22, 2014 6:13 pm
by SuperDave1426
doctorkb wrote:
SuperDave1426 wrote:Ok, thanks. I wonder if he can be persuaded to add State Managers, at least within the states they manage....


I doubt it. I suspect that he's using a "CM" flag that is applied to a user's record by the Waze system.

To expand it to anyone else would have to be to "AM" or everyone... unless he did a username-by-username validation.

Oh, maybe I misunderstood then. I thought that I had read somewhere that Waze actually created an official State Manager designation in the system. You're right, if all they did was just make us AMs with an area the size and shape of our states, then he'd have no way to tell the difference.

Re: [Script] WME Validator 1.0.4 / 24.08.2014

PostPosted: Sun Aug 24, 2014 3:17 pm
by SuperDave1426
Thanks for the quick fix on those! I trust those checks will be re-enabled at some point? :-)

Re: [Script] WME Validator 1.1.1 / 30.08.2014

PostPosted: Sat Sep 06, 2014 3:06 am
by SuperDave1426
Taco909 wrote:Thankfully, the combination of URO+ allowing cameras to display at Zoom-1 and 2 and the invalid mass camera deleter script makes life easier.
https://greasyfork.org/scripts/2377-wme ... ass-eraser


How do you set URO+ to adjust how far out cameras show up? I can't seem to find a setting for that...

Re: [Script] WME Validator 1.1.1 / 30.08.2014

PostPosted: Sat Sep 06, 2014 5:52 am
by SuperDave1426
Ok, thanks. :-)

Re: [Script] WME Validator 1.1.1 / 30.08.2014

PostPosted: Sat Sep 20, 2014 3:25 pm
by SuperDave1426
crazycaveman wrote:
BellHouse wrote:
crazycaveman wrote:Would it be possible to add a check for service roads in the USA? They have been deprecated and aren't to be used. Having them be highlighted (even if it's just as a note) would make it easier to remove them.

You can achieve that with the following custom check:

Custom template: ${typeRank}
Custom regexp: 9

Yeah, I've been using that. I was just thinking that, since this is a country-wide guideline, it would help more people be aware not to use that road type. Also, it would free up one of my custom checks :D

+1

Olestas wrote:You can also use WME Color Highlights for this.

I understand what you're saying there, but - given that Validator's purpose is to highlight things which need attention, and given that "service road" is a type that they want us to avoid using in the US, wouldn't it make more sense to add it as a check within Validator?