Regarding length: This was a while ago, but some time ago staff told us segments longer than 10 km (or 10 mi?) could cause routing problems. That may not be the case anymore, and in fact, I'm relatively certain I've routed over longer segments problem-free. Either way, the check should certainly be longer than 1 km.
--
Regarding the two-way default feature:
What I mean is that the box should be unchecked by default in both editors. Otherwise, users who are not aware of the change when Validator auto-updates may inadvertently start drawing 2-way segments where 1-ways are needed.
A couple beta editors mistakenly thought that the two-way default was a new beta editor feature, rather than a new Validator feature.
It causes confusion. There is no notice when Validator updates. All of a sudden something is behaving differently, unless you read the thread or check in the settings. It wouldn't be such an issue if the script had to be updated manually, but the fact that it silently auto-updates means you can start editing and be none the wiser.
--
Regarding the two-way default feature:
What I mean is that the box should be unchecked by default in both editors. Otherwise, users who are not aware of the change when Validator auto-updates may inadvertently start drawing 2-way segments where 1-ways are needed.
A couple beta editors mistakenly thought that the two-way default was a new beta editor feature, rather than a new Validator feature.
It causes confusion. There is no notice when Validator updates. All of a sudden something is behaving differently, unless you read the thread or check in the settings. It wouldn't be such an issue if the script had to be updated manually, but the fact that it silently auto-updates means you can start editing and be none the wiser.
Re: [Script] WME Validator 0.5.0 (BETA) / 20.01.2014