OpenCPN Beta Version 3.3.2330 Released

[nohal]

Originally Posted by fgd3

That's good news. I knew it was coming because it was mentioned earlier in the thread. One of the problems with overzooming a vector chart is the text doesn't get any bigger, so making it "like raster" will be a welcome improvement. Does that mean "like raster" will replace the blur?

On my Linux installation I had a dickens of a time making the change. The config file is in a hidden folder and I didn't know how to make it visible. Fortunately I had Internet access to help. I went the long way around, using terminal to rename .opencpn to opencpn, then going back to the File Manager to edit the now visible file with a text editor (couldn't remember how to use vi). Then I renamed opencpn back to .opencpn. Later I discovered I could have simply made the hidden files visible in File Manager from the View menu. ( I'm still used to looking for the menu at the top of the window, Windows style.) I'm not sure why I thought knowing Unix 30 years ago would make me knowledgeable enough to run Linux. It's working fine now.

Fabbian

vi ~/.opencpn/opencpn.conf

[fgd3]

Originally Posted by bdbcat

Gilletarom, et al...

Re on-screen scale.

...
Opinions?

Dave

Have you considered displaying the source chart's scale, regardless of how it is zoomed, followed by a zoom factor? (Maybe change the label to "Chart scale".) Without knowing the pixel density of a given screen there's no way you can figure an accurate scale. The original scale tells the user something about the density of data on the chart and the zoom factor lets him come up with some sort of calibration if he really wants to take measurements from the screen. Why would anyone want to do that when the computer will measure distances for him, regardless of zoom factor?

Fabbian

[HappySeagull]

determine which shortcut(s) have no accessible mouse or finger equivalent?

Originally Posted by wdkester

Using the current help shortcut list-

I think most of the orphans have found a home in the new menu bar,
the exceptions are F5, F6, F11. Maybe these too can have a presence in the menu bar. F6 as a slider maybe.

Correct my additions and we should have it pretty quick

F5,F6,F11, plus...

A toggle bottom features?
M measure =mouse right click context
[ tilt left
] tilt right
\ undo tilt
CTRL+B, G, I, M, N, O, R

Not needed on Tablets? but... Alts except Alt+arrows,

ESC...but Android back button would suffice?

[Hakan]

Dave....
I think I then also must show what your code can do although it shouldn't be possible. Be proud and please don't see it as a bug.

In this sequence I start with CM93 and the only events here are me zooming in several steps, the first row, and then out in steps, the second row.
It starts with CM93, transfer via BSB until a TM-KAP and then the same pattern out again ending in CM93.
What I've noticed is that the only occasion when a sequence is working like this is when the KAP chart covers the whole screen. After a KAP-BSB quilt CM93 is lost, but that's ok.
As said: WinXP, OpenGL and a fantastic 3.3.2330.
Thanks/Håkan

[wdkester]

Mistake on previous post. F11 is on menu bar.

[wdkester]

Can't seem to find "Lock Waypoints". It used to be on the Options>Display page. It's nice to unlock WP when creating routes.

[Mollymawk]

Originally Posted by bdbcat

Gilletarom, et al...

Re on-screen scale.

This issue is a bit annoying, really. OCPN uses the native operating system's idea of monitor resolution and actual pixel density. It makes no assumptions or conversions from that.

However, it turns out that Windows intentionally does not report the true physical dimensions of the screen, even if it knows.
I guess Mac does not either. This really surprises me, since Mac has historically been a relatively closed environment. Surely it knows, especially on a laptpop?
Both report a screen physical size that assumes something, but that something is not well documented.

So, what to do?
We could put a Options setting field to allow the user to enter the true monitor DPI, if known. We would default to something that makes sense for an "average" display, what ever that might be. Probably mine

Or, we could simply state in the Wiki that the scale reported on screen is a relative number, not intended for actual measurement with a caliper.

Opinions?

Dave

Dave,

OS X does correctly report screen resolution somewhere, since it works for native apps. But perhaps wx doesn't pass it on to us...
Maybe there is a way to read it directly from the system frameworks?

I think we do need to get it right (or somewhat closer than at the moment), as it means that the displayed scale is (for me) nearly double the real scale, which affects things like overzoom too (O thinks it is at 10x overzoom when it is really at 5x, etc).

What do you think of my idea of turning the "chart scale/zoom weighting" slider into a "screen dpi" slider/option?

Caesar

[colemj]

Since we are on MacOS and screen resolutions, etc, ever since about two Beta's ago, I notice that launching OCPN changes my monitor colorsync profile. At first I thought it was because it was using the other graphics processor (I have two of them in my laptop), but after turning one off, it still does this. I never noticed this happening with older versions.

It really isn't a problem, since I don't rely on accurately calibrated colors for OCPN. However, the color profile will not revert until OCPN is close, so any other programs that use a calibrated profile cannot be run while OCPN is loaded.

Could be something local with my machine - any ideas?

Mark

[rgleason]

So, what to do?
We could put a Options setting field to allow the user to enter the true monitor DPI, if known. We would default to something that makes sense for an "average" display, what ever that might be. Probably mine

I'd favor this with ability to enter screen height and width with a scaling factor and/or pixels ____ x _____

We do this for CAD to get the proportions of drawings appearance to correct.

[RhythmDoctor]

Originally Posted by wdkester

Using the current help shortcut list-

I think most of the orphans have found a home in the new menu bar,
the exceptions are F5, F6, F11. Maybe these too can have a presence in the menu bar. F6 as a slider maybe.

F5 has a button on the toolbar.

F11 is in a context menu, but only in tablet mode. I've requested to give it a more permanent presence in all modes (via toolbar icon or Options screen), and hope that will be done in next beta.

[bdbcat]

Caesar...

On Mac, as usual, wxWidgets is lame:
Here is the code that wxWidgets uses internally.

void wxDisplaySizeMM(int *width, int *height)
{
    wxDisplaySize(width, height);
    // on mac 72 is fixed (at least now;-)
    double cvPt2Mm = 25.4 / 72;

    if (width != NULL)
        *width = int( *width * cvPt2Mm );

    if (height != NULL)
        *height = int( *height * cvPt2Mm );
}

re: slider..
What do you think of my idea of turning the "chart scale/zoom weighting" slider into a "screen dpi" slider/option?

Nope. Not the same thing, in my mind, although coupled. Calling it a "DPI" slider will not be intuitive. And the effect of this slider is subjective anyway.

Though, if we had an exact, reliable dpi number, we probably could do some calculations internally and eliminate the control entirely. Just figure out dynamically what slider value produces a "nice" display. Needs more thought.

I think we really need a fixed number "DPI". We select a default. We allow users who care about exact scale to adjust the number digitally, based on the specs of their machine. Pavel linked a nice chart...

Dave

[bdbcat]

Mark...

re Mac color temp changes...

We have done nothing on purpose to change this in months.
If you have saved the older Beta DMGs, maybe you could discover when it changed, to give us a clue?

Thanks
Dave

[HappySeagull]

ah,the menu bar! forgot that
F5
F6
[ tilt left
] tilt right
\ undo tilt
CTRL+ G, I, N,

WD,Look in Toolbox/Display/Advanced for "LockWpts"

Not needed on Tablets?all the Alts ?

ESC...but Android back button would suffice?

[jonasaberg]

Originally Posted by bdbcat

We do not attempt to quilt TM charts. They just don't play nice with our Mercator canvas. Long discussions in the past about this, various attempts, but nothing satisfactory.

Dave,
After releasing v4.0, laying back for a while, counting clouds with a smile of confidence for a job well done....

Maybe this with quilting TM could be worth a second look for v4.2? I seem to remember that other programs succesfully quilt TM .

I was meaning to check flyspray, but the site seems down?

/Jonas

[fgd3]

Originally Posted by nohal

vi ~/.opencpn/opencpn.conf

Thanks. That part I remembered. I was afraid I wouldn't remember the commands in vi to exit the program with the file saved in the right place.

The image you attached was slightly blurred. Is that part of the FogOnOverzoom effect or just an artifact of OpenGL?

Fabbian