OpenCPN Beta Version 4.6.22

[transmitterdan]

Originally Posted by Gilletarom

Dave :

Other item not present in crowdin :
- Local CPU clock
- Local GPS clock
- Local Sunrise/Sunset


Question : What is the difference from these two instruments :
- Sunrise/Sunset
- Local Sunrise/Sunset

Thank by advance.

Gillatarom,

Local CPU clock is the time as reported by the computer running OpenCPN. It uses the time zone of the computer.

Local GPS clock is the time as reported by the GPS NMEA data stream. The GPS always sends UTC time but this gadget converts the UTC time to the local time zone of the computer running OpenCPN. Sometimes this is not what you want so there is a new setting on Dashboard Preferences that controls the local time zone offset from UTC. If you set the offset to 00:00 then the offset comes from the local computer time zone. But if you set the offset to something other than 00:00 then that offset is added to the UTC GPS time to produce local GPS time.

Note that Local CPU Clock and Local GPS Clock will not usually be the same because they come from different clock sources. When playing VDR files the GPS clocks will follow the time as recorded in the VDR file.

Sunrise/Sunset is the same as it always was. It displays the sunrise and sunset times based on the current GPS coordinates as computed from GPS UTC time and date. The time is displayed in UTC with no offset. Most people outside the UK and Ireland don't think about sunrise/sunset in UTC time.

Local Sunrise/Sunset is the same as the old UTC Sunrise/Sunset except a time zone offset is applied using the same logic as Local GPS Clock. This allows to see sunrise/sunset estimates with times that more closely match your ship's clock or watch.

[Gilletarom]

Dave,

If you open the "Options/Conections" then you use the NMEA window, this window desappear immediately under the "Options/connection" window. Not good.

[transmitterdan]

Gilletarom,

This is the desired behavior in my opinion. The NMEA debug window remains open after you close the connections dialog. The debug window is not part of the connections process. I don't think we should change anything about how this works.

[Gilletarom]

hello Transmitterdan,

Originally Posted by transmitterdan

Gilletarom,
This is the desired behavior in my opinion. The NMEA debug window remains open after you close the connections dialog. The debug window is not part of the connections process. I don't think we should change anything about how this works.

I only defended OpenCPN users who are not "specialists" in computing and / or OpenCPN. This can only destabilize them. And some must think this is a software bug.

[Hakan]

TD..
I could agree it's rather annoying the debug window is hidden behind the options window. You've to know where it is and move the options window to show it. And maybe resize the debug window for next time.
If the debug windows was located slightly beside the options window instead of covered behind, everyone would be able to notice it?
Håkan

[transmitterdan]

I will have a look but this behavior is unchanged since many years. It may be possible to have the debug window pop up somewhere other than the center of the screen. But we are seeing users with a huge range of screen sizes and resolutions. I think it's getting near impossible to make everyone happy. So we have to think carefully before making a change to a long standing feature/bug.

[Gilletarom]

Hello Transmitterdan :

Originally Posted by transmitterdan

I will have a look but this behavior is unchanged since many years. It may be possible to have the debug window pop up somewhere other than the center of the screen. But we are seeing users with a huge range of screen sizes and resolutions. I think it's getting near impossible to make everyone happy. So we have to think carefully before making a change to a long standing feature/bug.

Hum ... No, I do not agree. From memory, this dates from O4.6 or O4.6.1. And I still say it's unpleasant to use, even with my Lenovo PC which has a pretty big screen.

And I had really problems with my GPS while sailing a few days ago. I had to go back to the options to resolve this. I was annoyed not to see the options and the NMEA window simultaneously.

Gilletarom

[Hakan]

Gille..
You can use them simultaneously. Just slightly move the options window so you can "reach" the debug w.
TD..
Everyone can never be happy. Most can sometimes be slightly happier. But I do agree the answer is always 42.
Without making this a big effort - Instead of center the debug window could it be located off center, say 20% of screen size?
Håkan

[CarCode]

Originally Posted by Hakan

Without making this a big effort - Instead of center the debug window could it be located off center, say 20% of screen size?
Håkan

It should be in front when activated and not behind anything. This is the behavior for any application. It seems the so called developer cannot do it...

Gerhard

[Hakan]

TD...

If I remember correct there's a historical struggle with this. Tracing the code back there's a good attempt to position this window in a good place. And I also think the behavior for this window is different for every? OS.
So finaly, when it was hard to satisfy every OS someone get tired and simply centered the window and though by-passed all good attempts and also the saved last position.
See NMEALogWindow.cpp around row 60:

void NMEALogWindow::Create(wxWindow * parent, int num_lines)
{
    if (window == NULL) {
        window = new TTYWindow(parent, num_lines, this);
        window->SetTitle(_("NMEA Debug Window"));

        // Make sure the window is well on the screen
        pos_x = wxMax(pos_x, 10);
        pos_y = wxMax(pos_y, 10);

        window->SetSize(pos_x, pos_y, width, height);
#ifndef __WXMSW__
        window->Centre();
#endif
    }
    window->Show();

The "ifndef __WXMSW__" is my, also simple, test to partially solve it for Windows. With this last showed position will be reused next time. You may have better ideas?

And #Gerhard; If the solution is that simple for all OS could you please give us a lesson and show how?
And I don't think it's that easy to just load it up front. It can be we still want the options window on focus?
Håkan

[CarCode]

Originally Posted by Hakan

And #Gerhard; If the solution is that simple for all OS could you please give us a lesson and show how?
And I don't think it's that easy to just load it up front. It can be we still want the options window on focus?
Håkan

Sorry but I know these problems. Therefore I changed the code for myself to my own version to be used only for macOS. The goal to write a software for any OS has its limits as you see with this example. There are many others, think about what a Retina display can do e.g.
Some OS distributers have guides for developers how to program user interfaces. They are all badly ignored by OpenCPN. A good software should intuitively be used without reading tons of manuals. OpenCPN is the opposite.

Gerhard

[transmitterdan]

Originally Posted by Gilletarom

Hello Transmitterdan :



Hum ... No, I do not agree. From memory, this dates from O4.6 or O4.6.1. And I still say it's unpleasant to use, even with my Lenovo PC which has a pretty big screen.

And I had really problems with my GPS while sailing a few days ago. I had to go back to the options to resolve this. I was annoyed not to see the options and the NMEA window simultaneously.

Gilletarom

Gilletarom,

With OpenCPN not running you can manually edit opencpn.ini and look for these two lines:

NMEALogWindowSizeX=600
NMEALogWindowSizeY=400

Change these numbers to a size that you like for your screen. The size is in screen pixels. Then start OpenCPN.

The debug window always appears in the centre of the screen when the check box is selected. This is by design. If the debug window is too small so that it is covered by the options screen then changing the size in the ini file will make the screen bigger and then it can be easily seen.

However, it is important that the debug window pop up behind the options dialog. If the debug window were to completely cover the options window then you could not see the options window. You would have to move the debug window around to find the options window and close it.

So I think the best solution for you is to try editing the ini file and see if you can set a size for your display that works for you.

[transmitterdan]

Originally Posted by CarCode

It should be in front when activated and not behind anything. This is the behavior for any application. It seems the so called developer cannot do it...

Gerhard

The developer is trying to make things simpler for people. If the debug window is on top of and large than the options window then the options window cannot be seen without moving the debug window. So for most people having the windows stack up so they can all be seen is the best option. In the .ini file one can select the size of the debug window so it can be optimized for any particular user's screen.

It is a tradeoff. Some people like it one way and some people who may have not used it much think they would like it another way.

Honestly, I am getting tired of a non-contributor throwing personal insults at people who are actually contributing to the project.

[P_Dub]

Take it easy my friend you are doing an excellent job and I encourage you to keep on doing it. Unfortunately, some of us would like it more but one must consider that it is volunteer and everyone can help if it please him to do so.
Thanks for your kind help.

[Gilletarom]

Originally Posted by transmitterdan

Gilletarom,
With OpenCPN not running you can manually edit opencpn.ini and look for these two lines:
NMEALogWindowSizeX=600
NMEALogWindowSizeY=400
.......

Every day that passes, I screw my head against the walls because I am not able to program. So I have to accept that this regression of OpenCPN will remain a boards are OpenCPN regression.

That said, thank you Transmitterdam for your personalized advice.
Obviously, these tips are difficult to offer to alpha or beta users and even to experienced users.

Gilletarom.