OpenCPN Beta Version 3.3.2410 Released

[bdbcat]

Gilletarom...

regarding your previous post, Heading vs Course.

Is it possible that the developers definitely agree on the following rule:
- Each time that the word "Course" is used, it will designate the "COG"
- Whenever the word "Heading" will have meaning "Magnetic course."
- Never the word "Course" will be used instead of "Heading" and vice versa.

With slight refinements, this is OK. We must drop item 2. There is almost always a difference between true and magnetic heading, and we must be precise. I propose that "Heading" mean "True Heading", and that "Magnetic Heading" be used when that is the meaning in context.

With that, can you see any discrepancy in the OCPN base code with regard to these rules? PlugIns are another thing....

Thanks
Dave

[bdbcat]

Gilletarom...

re:
When we choose to check "Look ahead mode", it is not possible to select the update period.
It would, in the "Options / Display / Advanced" a similar box that already exists for the update period in the case "Course Up".

Not sure what you mean here. Look ahead mode simply changes the location of the ship on the screen, but is updated at the same rate as usual, generally once per second.

Dave

[bdbcat]

Jean Pierre (ptizef)

Regarding your OpenGL trouble with "Suppress display emphasis..."

Will you post your log entries for the OpenGL configuration?

Thanks
Dave

[bdbcat]

Håkan..

About Intel OpenGL on linux:

Here is my logfile stuff. This OpenGL setup works fine on Ubuntu 12.04

21:08:37 EST: OpenGL-> Renderer String: Mesa DRI Intel(R) Q35 x86/MMX/SSE2
21:08:37 EST: OpenGL-> Detected Intel renderer, disabling stencil buffer
21:08:37 EST: OpenGL-> Texture rectangle format: de1
21:08:37 EST: OpenGL-> Using Vertexbuffer Objects
21:08:37 EST: OpenGL-> Using Framebuffer Objects
21:08:37 EST: OpenGL-> Using FBO Stencil buffer
21:08:37 EST: OpenGL-> Using Depth buffer clipping
21:08:37 EST: OpenGL-> Using s3tc dxt1 compression
21:08:37 EST: OpenGL-> Compressed tile size: 128kb (6:1)
21:08:37 EST: OpenGL-> Minimum cartographic line width:  1.0
21:08:37 EST: OpenGL-> Minimum symbol line width:  1.5

Compare, please.

Thanks
Dave

[Gilletarom]

Hello dave,

Originally Posted by bdbcat

Gilletarom...
.....
Not sure what you mean here. Look ahead mode simply changes the location of the ship on the screen, but is updated at the same rate as usual, generally once per second.
Dave

It is precisely when the boat changes direction often, for example every second, it becomes unpleasant to live because the whole chart that suddenly changes constantly.

That said, it must also be easy to implement. Otherwise, do nothing.

[bdbcat]

cagney...

re:
I managed to catch an abnormal display of tidal stations.

I see this too. You may have noticed the scale factors calculated and shown in the status bar were non-sense when this happens.

Simple fix, relates only to very small scale display of cm93.

In github now.

Thanks for the catach.
Dave

[bdbcat]

Gilletarom...

Re Look ahead.

So it seems that COG-up filtering does not work in look ahead mode?

Maybe. I will investigate.

Thanks
Dave

[Gilletarom]

Hello Dave,

Originally Posted by bdbcat

Gilletarom...
regarding your previous post, Heading vs Course.
...the following rule:
- Each time that the word "Course" is used, it will designate the "COG"
- Whenever the word "Heading" will have meaning "Magnetic course."
- Never the word "Course" will be used instead of "Heading" and vice versa.

With slight refinements, this is OK. We must drop item 2. There is almost always a difference between true and magnetic heading, and we must be precise. I propose that "Heading" mean "True Heading", and that "Magnetic Heading" be used when that is the meaning in context.
....
Dave

That suits me.

But what bothers me is that you seem to say that you can not impose this rules developers plugins.
It is precisely because of the plugins I have been led to start this debate.
Indeed, I would never have started this debate if the plugin language file did not crush the general language file (item by item).

B.R. Gilletarom.

[bdbcat]

Gilletarom...

It is difficult to change the existing PlugIns. We have said that legacy PlugIns will always work with an OCPN core upgrade, so we cannot insist that older PlugIns be "fixed" and re-released. Many of the authors are gone...

We certainly can set this policy for the future..

Which PlugIns are giving you trouble now?

Dave

[NahanniV]

Originally Posted by Littlechay

What we don't have in OpenCPN is a "course up" mode. What we have is "heading up" and this can cause the screen to keep flicking back and forth as the boat yaws in any kind of sea. I can see the rotation keys being used to align the chart to course up to avoid the heading changes due to yaw affecting the display.




Sent from my iPhone using Cruisers Sailing Forum

I think the term should be "Track" up. Besides testing, this is what I use the rotation keys for, perhaps it could be automatic if the data is available or manual by keyboard if not.

Cheers,
JM.

[bdbcat]

Gilletarom...

Thinking more about PLugIn translation overrides...

It may be possible to create a method where PlugIn translations do not replace an existing core translation, if it matches exactly.

Would this resolve your difficulties?

Thanks
Dave

[Gilletarom]

Originally Posted by bdbcat

Gilletarom...
Thinking more about PLugIn translation overrides...
It may be possible to create a method where PlugIn translations do not replace an existing core translation, if it matches exactly.
Would this resolve your difficulties?
Thanks
Dave

Hello Dave,

Indeed, if you solve this old problem, then you not only have solved "my" problem, but that of all translators.

I think I can advance thank you on behalf of all translators.

That said, it does not completely solve the problem of meaning given to the word "race" and "Heading". The solution we discussed should not be forgotten.

Just read the post Littlechay, in this thread, and two or three answers that have been made to him to measure the significance of errors in understanding the meaning of these two words. I have observed similar problems in France in some thread on our forums.

Best regards. Gilletarom.

[Ptizef]

Originally Posted by bdbcat

Gilletarom:

re:
On the map rotation with the shortcuts "[" or "]"?

I never managed to make it work. Is it really implemented? Or the radio button for "north up" or "COG up" he prevents the operation of the keyboard shortcuts?

Works fine for me in all cases. Maybe it is a French keyboard difference? Any other users with French kb may test?

Thanks
Dave

Dave

Don't work for me too (French keyboard)
Jean Pierre

[Gilletarom]

Hello Dave,

Originally Posted by Ptizef

Dave

Don't work for me too (French keyboard)
Jean Pierre

I ask PytheasF54 to test. He try. "[" and "]" do not run in his PC.

PytheasF54 PC : Fujitsu-Siemens Amilo, 15'. See joined screen shot.

I add that in a french keyboard, we use the key "Alt GR" before to use "[". Idem with "]".

B.R. Gilletarom

[Hakan]

Originally Posted by bdbcat

........It may be possible to create a method where PlugIn translations do not replace an existing core translation, if it matches exactly.
Would this resolve your difficulties?
Thanks
Dave

Dave...
Sounds good for me as well. There's a couple of similarities when translating to Swedish. For example "Range" is used both for a distance and an area, and these are quit different words in Swedish.
Thanks
Håkan