Waypoint circles Up !

[Didier B]

Example of the inconsistencies of waypoint circles radius :

here are 2 waypoints with the same declared radius: 0.035 NM
(CTRL+C, CTRL+V), the circles were added during the same session, within a few min interval .

Is it "radius" or "diameter" ? It seems even the code (5.2.0.9) doesn't know and randomly uses the value as a radius or a diameter


The issue was reported loooong ago ...

[rgleason]

Very clever. If you make such allegations, you are obliged to show exactly how you did this, including screens shots while making the waypoint circles! Otherwise it will be difficult to fix.

[Didier B]

Before saying I am a liar, tell me how it is possible to open the properties of 2 different waypoints at the same time to show them on the same screen shot !

[rgleason]

Didier I did not say you are a liar.
In windows when I try to open two waypoint properties the properties menu simply changes to the most recent, which seems reasonable to me.


There are two different things "Range Rings" and "Arrival Radius" so please explain your problem more clearly if possible.


I might help to read the manual about these two items.

[Didier B]

I am no more dumb than liar !


I am speaking of the rande rings (who are displayed on the screen)
This bug has been around for months now, almost a year ! It happens than some of those range rings are displayed with a doubled radius, already reported here : https://www.cruisersforum.com/forums...ug-225317.html


On same subjects please see also https://www.cruisersforum.com/forums...es-219088.html
Which happens periodically !

[rgleason]

Why don't you use the continuing thread?

https://www.cruisersforum.com/forums...ml#post2997467


Also see related thread https://www.cruisersforum.com/forums...ml#post2920891


I cannot currently see your posts in Tracker as I have been just locked out of the website and will need to wait 2 days or so. (I was trying to fix some problem in the "Send WPT to IP" page that keeps causing the website to shut my IP down).


So that's good that you think you are "no more dumb than a liar". I was just trying to understand the problem and help. I guess I'll just stop here as you get agitated because something hasn't been fixed.

[bdbcat]

DidierB...
I do not immediately see this issue in the Flyspray tracker.
Is it there, and I missed it?


If not, i remind all users that issues reported in the Forum outside of a formal Beta test cycle are often missed by the dev team. There is just too much traffic to catch everything as it flies by. Further, the devs are often fully immersed in new code/bug fixes, and so not in a position to immediately reproduce and address the bug.


Thanks for the report
Dave

[Didier B]

Originally Posted by bdbcat

DidierB...
I do not immediately see this issue in the Flyspray tracker.
Is it there, and I missed it?


If not, i remind all users that issues reported in the Forum outside of a formal Beta test cycle are often missed by the dev team. There is just too much traffic to catch everything as it flies by. Further, the devs are often fully immersed in new code/bug fixes, and so not in a position to immediately reproduce and address the bug.


Thanks for the report
Dave

Hi Dave,
In the tracker : https://opencpn.org/flyspray/index.p...rom=&closedto=


I don't quite understand how it is managed :

• Severity : high
• Priority : Very low
• Due for version : not decided
• Due date : Not decided

Explained in the text : "It could cause gross errors in navigation with implications for safety, for obvious reasons."


Is there is something I can or should do to ease the correction planning ?

[bdbcat]

DidierB...
I see the Flyspray task now. Well written. In the correct place.


We have no specific plans for an upgrade to OCPN 5.2, yet.
We probably would not classify this bug as critical enough to warrant a Release on its own. So the bug will be addressed in due course, as we plan our next release cycle.


Thanks for the report
Dave