Tough Time with Charts

[bdbcat]

Gerhard....

It is no secret. All the code is there to read by all.
If you actually read the code in context, with embedded comments, you will see this:

   //  Windows installer may have left hints regarding the initial chart dir selection
#ifdef __WXMSW__
    if( g_bFirstRun ) {
        int ndirs = 0;

        wxRegKey RegKey( wxString( _T("HKEY_LOCAL_MACHINE\\SOFTWARE\\OpenCPN") ) );
        if( RegKey.Exists() ) {
            wxLogMessage( _("Retrieving initial Chart Directory set from Windows Registry") );
.
.
.

This code runs exactly once, on initial load from bare metal.
You will also not find any code that writes to the registry.

Would you like to tell why you have never submitted a single line of code to the OCPN projects, despite continual sniping? It is tiresome....

Dave

[tbenefield]

At the bottom of the directory that contains all the CM93 chart directories are a hand full of files. Most of them end in .dic. For some reason when I copied the charts to my new computer, these didn't make it. I simply copied them into the chart directory and all was good.

[CarCode]

Originally Posted by bdbcat

Gerhard....

It is no secret. All the code is there to read by all.
If you actually read the code in context, with embedded comments, you will see this:

   //  Windows installer may have left hints regarding the initial chart dir selection
#ifdef __WXMSW__
    if( g_bFirstRun ) {
        int ndirs = 0;

        wxRegKey RegKey( wxString( _T("HKEY_LOCAL_MACHINE\\SOFTWARE\\OpenCPN") ) );
        if( RegKey.Exists() ) {
            wxLogMessage( _("Retrieving initial Chart Directory set from Windows Registry") );
.
.
.

This code runs exactly once, on initial load from bare metal.
You will also not find any code that writes to the registry.

Would you like to tell why you have never submitted a single line of code to the OCPN projects, despite continual sniping? It is tiresome....

Dave

Fortunately I know to read the code. Therefore I wonder why
- you allow your installer to store settings in the Registry
- your code read settings from the Registry
- you don't kill these settings in the Registry

Someone said this was left behind of an old 1.x.x version of OpenCPN.
But I see this in Windows10 which doesn't exists at the time of an 1.x.x OpenCPN version.

European people are always scared about their privacy and don't prefer spyware. Sadly Windows10 is known here for gathering too much user data for unknown reasons.

I don't send a single line of code to you because you ignore it anyway.
Times ago e.g. I have pointed you to your wrong usage of sizer attributs.
It was wrong with old versions of wxWidgets but does not throw an assert as it does now with newer versions. The rules are very simpel:
- don't use horizontal alignment flags together with wxWXPAND
- don't use vertical alignment flags together with wxWXPAND
- don't use horizontal alignment flags for horizontal sizers
- don't use vertical alignment flags for vertical sizers
Until up today you ignore that.

Other things are rather stupid for me: Making the chart display unvisible with fogging is e.g. the worse thing I ever have seen. Maybe you don't like any critics but it should allowed to express it.

Gerhard

[bdbcat]

Gerhard...

re:
It was wrong with old versions of wxWidgets but does not throw an assert as it does now with newer versions. The rules are very simpel:

These asserts have no affect at runtime. They are ignored. So this kind of compile-time warning is generally low priority to me, compared to larger scale functionality.

However, if that is important to you, or critical to your workflow, then submit a Pull Request fixing it. It will be considered like any other. Pull Requests improving the coding style are rarely rejected, as you may observe by history.

Dave

[CarCode]

Originally Posted by bdbcat

Gerhard...

re:
It was wrong with old versions of wxWidgets but does not throw an assert as it does now with newer versions. The rules are very simpel:

These asserts have no affect at runtime. They are ignored. So this kind of compile-time warning is generally low priority to me, compared to larger scale functionality.

However, if that is important to you, or critical to your workflow, then submit a Pull Request fixing it. It will be considered like any other. Pull Requests improving the coding style are rarely rejected, as you may observe by history.

Dave

You know very well that any assert is suppressed in a release version. But in debug mode you have nice hints where your code is dirty.

And I dislike the new english language where people are talking about so called "alternative facts" when the real true facts shows something else.

Gerhard

[rgleason]

Gerhard I can agree with you, sometimes, but keep in mind that Americans are all very different, because we are from many different places. We don't all think alike. Might that be true in Germany?

[CarCode]

Originally Posted by rgleason

Gerhard I can agree with you, sometimes, but keep in mind that Americans are all very different, because we are from many different places. We don't all think alike. Might that be true in Germany?

Better not to become political, it might be dangerous...

[rgleason]

Agreed.