OpenCPN Version 5 Beta Starts

[Hakan]

Originally Posted by nohal

@Hakan, @conachair...
The route dialog field focus mess started by leaving the "Plan speed" field for the first time seems fixed for me in current github master, can you confirm?

Thanks

Pavel

Yes, Very good now.
I can edit the field, leave it by the tab key or a mouse click somewhere else and return for another edit.

Thanks
Håkan

[Hakan]

Originally Posted by yachtvalhalla

Don't think this is important enough to call a 'bug' but it is very annoying.
When importing multiple waypoints they are sorted 'ZtoA'.
Clicking on 'Waypoint Name' changes it to desired (my) 'AtoZ'.
Terry the Nitpicker

I agree about the annoyance. The outmost feature would be if last sorting method, name or distance etc, was saved as for the AIS target list.

And I think it's good when we are at the nitpicker stage Then the hard work devs have made to get to this very fine O ver.5 is soon finalized.

Håkan

[nohal]

Originally Posted by yachtvalhalla

Yes the issue is still in this version.
Thanks, Terry

Then I can't reproduce. Anybody else?

[Hakan]

While on the routemanager.
I earlier slightly mentioned about the date formats. Let me explain more:
It's very good indeed you've the local system date format in the Departure field. That's an enhancement from before versions. But is it possible to get the same for the ETA and Tide info fields?
I saw the code and won't try to touch that part to much.


The US date format is very unusual for us from the other side of the pool. So many folks her have difficult to understand it. Unless the numbers don't tell you we don't know what's the month and the date.
Håkan

[Hakan]

Originally Posted by nohal

Then I can't reproduce. Anybody else?

If where talking about this:

Once the tide station has been found and the data displayed, it cannot again be displayed until O5 has been restarted

No I can't reproduce using a build from today's Github.
Håkan

[yachtvalhalla]

The Tide Station icon in version 4.99.1408+bbfdb68 is oversize compared with version 4.99.1408+0395280.

Flyspray #2492

NOTE: The tcdata with OpenCPN does not cover my part of the world. I am using a world-wide tcdata available here.

Might this be my problem here and for the disappearing tide stations on marks after first display?


Terry

[conachair]

Originally Posted by nohal

@Hakan, @conachair...
The route dialog field focus mess started by leaving the "Plan speed" field for the first time seems fixed for me in current github master, can you confirm?

Thanks

Pavel

Seems fine now, running out of things to break now

[bdbcat]

Terry....


re: Oversize tide icon...


What is the device/computer you are using for the screenshot shown?


Dave

[Hakan]

Dave..
Another example. Maybe not as huge as for Terry but bigger than before at least:
Win10. Today's Github, Object scale factor = 0.
Screen:
5:47:09 PM: Metrics: m_display_size_mm: 309 wxDisplaySize: 1366:768
5:47:09 PM: OpenGL-> Renderer String: Intel(R) HD Graphics 3000
5:47:09 PM: OpenGL-> Version reported: 3.1.0 - Build 9.17.10.4459


Håkan

[nohal]

Originally Posted by Hakan

While on the routemanager.
I earlier slightly mentioned about the date formats. Let me explain more:
It's very good indeed you've the local system date format in the Departure field. That's an enhancement from before versions. But is it possible to get the same for the ETA and Tide info fields?
I saw the code and won't try to touch that part to much.


The US date format is very unusual for us from the other side of the pool. So many folks her have difficult to understand it. Unless the numbers don't tell you we don't know what's the month and the date.
Håkan

Hakan...

Feel free to play with https://github.com/OpenCPN/OpenCPN/b...utePoint.h#L37 - As you can see on the line bellow I already did and honestly the locale-dependent short date format is the best I am able to come with. The date picker format we can't change at all, WX decides how it wants to show it (And it is also platform dependent).

Pavel

[Hakan]

Pavel..
Since you succeed for the departure field I thought you may have an idea also for the ETA fields.
I'll of course have a look but if you can't find a way how do you think I would?
Thanks
Håkan

[rgleason]

Maybe the date format should be a global choice, and all instances follow?
In any case it should be consistent as I suggested before. I almost wrote , of course I prefer the US way...except.

Originally Posted by nohal

Hakan...

Feel free to play with https://github.com/OpenCPN/OpenCPN/b...utePoint.h#L37 - As you can see on the line bellow I already did and honestly the locale-dependent short date format is the best I am able to come with. The date picker format we can't change at all, WX decides how it wants to show it (And it is also platform dependent).

Pavel

[Hakan]

Originally Posted by rgleason

Maybe the date format should be a global choice, and all instances follow?
In any case it should be consistent as I suggested before. I almost wrote , of course I prefer the US way...except.

Very good! Betcha.

https://www.cl.cam.ac.uk/~mgk25/iso-time.html
Håkan

[nohal]

Originally Posted by Hakan

Very good! Betcha.

https://www.cl.cam.ac.uk/~mgk25/iso-time.html
Håkan

Hakan...

ISO date is nice, but:
- The WX datepicker control will not use it unless we rewrite it, in which case we can rewrite it differently as well.
- You will create another group of user complaining they do not like it.

Your locale seems not to be set correctly but to English (Same as mine), if you switch to your correct native locale, the %x format string will be formatting the date correctly.

Pavel

[houlejm]

Originally Posted by Hakan

Pavel..
Since you succeed for the departure field I thought you may have an idea also for the ETA fields.
I'll of course have a look but if you can't find a way how do you think I would?
Thanks
Håkan

Hakan


Which language do you use? I am using French (Canadian) and the dates (Departure and arrival) have the correct format (YYYY-MM-DD HH:MM).

I agree the date format could be made independent of the locale. Even those with a English locale could have a logic format for date and time,

Jean-Marie