The report is cleared automatically once you change either a template or a regexp field. I guess you changed your custom check after the scan has been completed. This is my best guess. A permalink would help.crazycaveman wrote:Am I missing something with regards to negated regex's?
Why my TODO list is so long then?myriades wrote:AFAIK, there is no bug in Validator.
There is no any harm having them available for all editors. The information to match is limited. For instance, there is no way to match editor's name.myriades wrote:And the personnal check should be something as optionnal and for advanced editors
Also there is no relation between editor's level and the ability to use regexps. Some people (with IT background, I guess) understand those regexps, some people don't. But anyone can ask for a help and then just copy-paste two lines.
That is what the Custom Check in Validator for - gets the job done. Instantly
Both of your regexps work fine with me and give exactly the same number of reported segments.crazycaveman wrote:This is the area I'm running the report in, if you want to try it yourself.
Make sure you do not put any spaces before the exclamation mark.
Ok, cool. At least now you'll be able to switch between one script or another.HavanaDay wrote:EDITED: I think I have narrowed it down to Highliter script. Unless it just magically starting working again.
Sorry, I have no Mac, so I can't check the issue
As suggested in other thread, here is the working link: userscripts.orgOlavoAG wrote:Where can I download it? userscripts.org seems not to be working...
For Firefox
Please try Settings->Reset defaults or just make sure your search tab has no options activated.
You can try ${segmentsA/B} and ${outA/B} variables, for example:TyrionGOT wrote:How would I create a custom expression to flag nodes with turn restrictions?
Template: ${segmentsA}:${outA}
RegExp: /3:[^3]/
This will match a segment connected to 3 other segments at node A, but having not 3 outward turns enabled.
But it's not that simple. You have to take into account segment's direction etc etc. So I suggest you use instead Shift+Z WME shortcut which shows you disabled turns.
Try to match length 0-9 OR 1 following 0-6:olestas wrote:How should I search for segments shorter then 17m?
Template: ${length}
RegExp: /^([0-9]|1[0-6])$/
Re: [Script] WME Validator 0.9.9 (BETA) / 27.04.2014