OpenCPN Version 2.4 Beta Build 412

[sailorF54]

Originally Posted by sinbad7

2. Full screen F10 (?) does not work

Tore

Shift F10 works on a French keyboard....

[sailorF54]

Originally Posted by manimaul

Hey guys, I've proposed this user interface simplification. Any input would be appreciated. FS#400
Feature/Changes:
1. Button bar/ribbon does not fill entire viewport (could also be made semi-transparent) (also could hide after timeout when mouse is not moving to give more screen realestate)

Ways to hide the button bar when using a small (e.g. 10") screen has often been mentionned on French forums....

[yantho]

[QUOTE=manimaul;667341]Hey guys, I've proposed this user interface simplification. Any input would be appreciated.


Very clean, light and modern, I vote "Yes"

[sailorF54]

Originally Posted by sailorF54

Crash ....

-

A clean install seems to have cured my problems....

However the CM93 offset function seems to have disappeared from the Toolbox

[HappySeagull]

Ah!thanks,sailorF54.Shift+F10 does the trick!

[NAV]

Suggest to change the text "Departure Time (m/d/j h:m)" in the route properties window to "Departure Time (jjjj.mm.dd hh:mm)". Probably has effect on the allowable input format.

[PjotrC]

Originally Posted by NAV

Suggest to change the text "Departure Time (m/d/j h:m)" in the route properties window to "Departure Time (jjjj.mm.dd hh:mm)". Probably has effect on the allowable input format.

I also would prefer the format you suggest. But I am using the general wxWidgets ParseDateTime function... according to the manual it should parse anything reasonable, but I am succeeding only with m/d/y I'm afraid we have to get used to it. I usually input ">" for "now", then just edit the required fields.

[Surveyor]

Concerning the button bar:

I propose to take it a step further and allow a choice of vertical or horizontal alignment of the button bar.

I assume that most users use the course up mode which happens to be the direction of the narrowest part of most screens. With the buttons stacked vertically on the side, there would be a little less on screen where you are going.

ANOTHER THOUGHT:
Would it be possible to set the default screen boat position, or allow a choice, from the center to some offset? Say if I am in course up mode, I want my boat to appear in the bottom, and stay there, allowing me greater vision of whats ahead.

[sinbad7]

Dan..

Using the chart display filter in vector charts causes a crash.
Both checking and un checking a filter item crashes OpenCPN.

Enable chart quilting crashes program.

Shift+F10 for 'Full screen' does not work in Vista...

Seems there are many problems in this version.

Tore

[Ptizef]

Originally Posted by Surveyor

ANOTHER THOUGHT:
Would it be possible to set the default screen boat position, or allow a choice, from the center to some offset? Say if I am in course up mode, I want my boat to appear in the bottom, and stay there, allowing me greater vision of whats ahead.

Looks like "Look Ahead Mode" in toolbox/setting
To calculate the offset , OpenCPN needs to receive data from the GPS and the boat moving

JP

[fgd3]

Originally Posted by Surveyor

Concerning the button bar:

I assume that most users use the course up mode which happens to be the direction of the narrowest part of most screens. With the buttons stacked vertically on the side, there would be a little less on screen where you are going.

That's funny, I assume most users use the north up mode, perhaps because that's my own preference. Maybe it would make sense to gather some actual data on that issue before making any changes based on one or the other assumption.

Moving the buttons from the top to the side is a good idea in any case, as the screen is wider than it is tall.

Fabbian

[HappySeagull]

Originally Posted by Ptizef

Looks like "Look Ahead Mode" in toolbox/setting
To calculate the offset , OpenCPN needs to receive data from the GPS and the boat moving

JP

But surveyor has an interesting idea...even though there's "look-ahead"already,it will vary as boat speed changes...that is,logically, one need speed up to see further ahead just when it might be better to slow down and see further (without having to zoom out).. having the boat generally off-centre seems a good idea...

That said,I haven't used the look-ahead feature in O myself so I'm relying on your description,JP, as to it's function.But I used to use it in other nav apps and also the predictor feature ...however, in my sailboat,they drove me crazy.The boat-on-screen was constantly jerking and the predictor line was growing,shrinking,swinging....

[Ptizef]

Originally Posted by HappySeagull

...however, in my sailboat,they drove me crazy.The boat-on-screen was constantly jerking and the predictor line was growing,shrinking,swinging....

That's quite true , but it can be stabilized a bit by using that new function in toolbox/GPS :
"Filter NMEA Course and Speed data" over few seconds at your choice which will average data thus smooth movements
You'll have just to find the good compromise between reactivity and stability
(I've not test it yet in live)
JP

[r.fairman]

1. Crash when clicking ok in toolbox
2.F10 does not work or Shift F10
3.When selecting right click object info only "chart" displays No object info
4.Extra minimised window in taskbar

xp sp3

regards

Richard

[nohal]

Originally Posted by r.fairman

1. Crash when clicking ok in toolbox

Richard...
Any preceding action? Anything suspicious in the log? Can't reproduce here.

Pavel