firecul wrote: ↑Sun Aug 28, 2022 1:03 pm

SebastianJM21 wrote: ↑Sun Aug 28, 2022 9:58 am
So the venue ID is correct but the coordinates seem to be messed up.

Chrome and Script (from Chrome Store) are both up to date.

 

Strange, that's what the most recent update is to fix. Is your script definitely v. 2022.8.25?

 

SuperDave1426 wrote:

iangpowell wrote:Click play, and it tells me "starting! layers are off to scan faster", and then nothing. It doesn't strictly crash, as I can still click around, and pause/stop, but no report appears and nothing else happens.

Yup, I can confirm this behavior as well. I've got Fix Map Objects installed, so at least it does its thing while I'm editing. But doing a scan to get a report goes nowhere.

Raiden38 wrote:I'm trying to do a custom code but I can't get it to work. Can you help me?

The goal is to highlight all the Primary roads that don't have a name, and they are longer then 50 ft.

First issue: it highlight some ramps
2nd issue: Depending on the test, it will highlight all roads bigger than 50ft!

Here is what I tried:

Code: Select all

  
   "131.enabled": true,
  "131.params": {
  "template": "${typeRank}#${street}@:${length}",
  "regexp": "/^1[1-5]#@:([5-9]+[0-9])$|([1-9]+[0-9]+[0-9])$/",
  "titleEN": "No Street Name on Primary Street",
  "problemEN": "No Street Name on Primary Street",
  "solutionEN": "Add the name",

/^1[1,3-5]#@:(([5-9][0-9])|([1-9]\\d{2,}))$/

jarkaz wrote:I wrote to him, but did not even read the message. [emoji20]

karlcr9911 wrote:It's a known issue that Validator isn't working in this latest WME release. The script writer has been contacted. If he chooses to update it, he'll do so as soon as he has time.

taco909 wrote:

Code: Select all

javascript:Waze.loginManager.events.triggerEvent('login');

It was working on the old version when using this login, but I haven't been able to get it to load on FF since it updated to .17

WME Validator v1.1.17: already logged in!