I made various tests with the last two versions of OD and WD.
, I mean no crash or other. Let's say it's Ok.
At my language file, to give it a try:
In OD, instead of "Exclusion", "Inclusion" and "Neither," I put "Grid inside", "outside Grid" and "No grid".
The items of OD are not overwritten by those of WD. It's Ok.
let's remember that :
A boundary consists of:
A limit (or border) closed, which divides the plane into two parts
: inside and outside (It's like Switzerland and the European Community)
I entered various items in OD and WD.
At the language file, I took an idea of Nevermind. I replaced "Exclusion", "Inclusion" and "Neither" to "Allow Entry", "Entry Denied" and "Nothing"
I took my tests with 6 polygonal boundary, activated 3, 3 inactivated. The interiors of the boundary do not overlap.
All tests with a VDR file have shown that activation and / or deactivation was properly taken into account. No problem at this level.
- They can be triggered when the boat comes within a "boundary".
- If they are activated by entering inside a boundary, they cease when the boat comes out..
- They never triggered when the vessel is leaving the interior
of a boundary.
Having said that, here is the summary of tests, only with activated boundary (That's short writing).
With "All": This sounds as soon as the boat comes within a boundary.
With "Allow Entry": This sounds when the boat comes within a boundary with the internal grid
With "Entry Denied" This sounds when the boat comes within a boundary with the external grid
With "Nothing": This sounds when the boat comes within a boundary without gridlines.
NOTA BENE :
Question: What happens to it especially if we interchange the text items "Allow Entry" and "Entry Denied"?
Answer: It does not change the operation. You can swap in English
, the items "Exclusion" and "Inclusion" in the window, it does not change the operation.
Question: The user can make a bad choice it inadvertently?
The risk, as choices "by mistake" in WD, whether committed by the user is always present. Therefore, it is possible that no alarm
is triggered, even when the user is expected to trigger it.
Please forgive me for this idea. I measure the disappointment that my words can cause. JonGough know that I have the feeling of a job that will lead, later, on a very good tool.
Personally, I suggest:
- This type of alarm
is inactivated in WD,
- What WD, without this type of alarm is posted,
- What changes are implemented.
- And later, a new version is posted.