Fredo-p wrote:Just how often do you guys use the tabs? I rarely click on them. When I do need them, and the sidebar is causing it to expanding, making a scroll bar, I just scroll down. It doesn't seem like that big of a deal. Even on a small screen (which has been my primary screen for years).


[UPDATE]

As for the Me tab. Yes, I was wrong. You had to be on the me tab to be able to see it. However, that was how I liked it. I liked having validator "always on".

For Validator?

I run reports all the time, and the Validator menu needs to be visible for that.
As a tab, it's just a matter of clicking back and forth between "Me/Validator" and whatever tab is being used.
Now, it's "go to the TB/URO+ tab, enable the annoying cartoon box, work with Validator, go back to the TB/URO+ tab, disable the annoying cartoon.....

It's an extra step and a bunch of scrolling.

Maybe wouldn't be so bad on a 32" monitor with a 4k display.

Fredo-p wrote:I have a 20" AOC. That's probably why I'm not having that much of an issue. If my laptop was working, my 15" would have me saying otherwise.

I'm running a Flatron 23" @ 1920x1080

My notebook is horrible.

KuniaKid wrote:Hawaiian city and street names use diacritical marks that are flagged in Validator, specifically the apostrophe. We get UR's that request that we match the signage. I haven't found any guidelines in this matter, so I add the mark. Is there a way to switch off the check for this in Validator?

Hawaii State Managers are in discussion as to using complete diacritical marks for all names. There is quite a movement here for making all things PC.

A localizer script can be written to augment Validator.
I'm not sure that it can disable the flags in the primary code, but it can add new flags based on local preferences including lock levels, street name conventions, etc...

Robert04101 wrote:Feature request: please add "Dead-end one-way segment" in reports. Such roads clearly can't exist in practice, but between base map errors and newbie editors creating one-way roads, I see a lot of these problem segments.

There certainly are places where these could be valid, specifically one-way stubs intended to force "stay" instructions where BC logic produces unclear or confusing results, but these should be locked 4+ anyways, and it never hurts to give them another look.

This WAS a feature of Validator until the WME changes of late 2014.
It was actually a flag for "No inbound/outbound connectivity of driveable segment" so not only did it flag dead end one-way segments, it also flagged segments with turn restriction issues.
We lost that at the same time we lost notification on RevCons and other junction-related problems.

Toolbox and Highlighter still do a good job of flagging things like RevCons, but Validator no longer includes them in the report screen. I miss that function.

SuperDave1426 wrote: If you simply have to do it that way, then I would agree with jdelosa about using the Settings or Drives tab.

I like the idea of using the settings tab.
Likewise for other scripts that have a minimal interface, such as Mass Camera Eraser (which currently appears above Validator)

aBshield wrote:I thought I'd flag this here in case this is something WME Validator could potentially test for. As I write this though, didn't we have something like this way back? Was this impacted by the same change that lost some other functionality?

We did.
"No inbound/outbound connectivity of driveable road"

That function went away in August 2014 when turn restriction data was moved from the segment to the junction (likely in preparation for JB). This was the same time we lost Validator visibility/flagging of Revcons and unconfirmed turns.

Given that Validator can pull flags from WMECH and TB, I would really like to get RevCon and Unconfirmed Turn flags back in the Validator report...
Getting back the "no inbound/outbound" may be more daunting as it requires the analysis of both the segment data (determine directionality and if routable) and the junction node, then comparing the two.
It may be too much complexity for what is essentially a fairly simple script.

I agree, it was a good feature when we had it (so long as that specific feature is locked so as not to display "errors" on segments locked above the editor's level, as there are many times that we create these intentionally)

Just received an update, appears to be working.

SuperDave1426 wrote:@khaytsus, believe me, you're not the only one who wishes that we'd get an option to put Validator on its own tab since access to the interface itself is needed so infrequently....

+1

Apparently some editors don't like having a second row of tabs... I have 3

Confirming, seems to be fine on Chrome, still broken on Firefox.

RealMrMonteCristo wrote:Hi guys!

I was just wondering, is there a way to get this to scan your editable area? I have looked around the script and this forum. But could not locate anything about that, I am guessing not?

Thanks!

Only if your editable area fits on one screen