OpenCPN Beta Version 4.8.10109

[bdbcat]

Bruce...

re:
I attached two charts for your reference. One is 505W and the other is 503E.

505W covers the area that screen shots that anchorage boundaries were missed. The lines were missing even without any correction.

503E attached here for a crash problem with the latest Android version. The program crash when correction file .033 was loaded.

I have resolved the problem with 505W. Indeed, the Anchorage areas were missing from STANDARD mode display. They do appear in ALL category, when toggled by 'A' key. The general solution will appear in next Beta.

On 503W, there was also a problem. I have seen your crashes on my Android developer feedback page. I corrected the cause of the crash for next Beta.

However, I find that there is still an error on update file .033 for this cell.
The update will not apply correctly. By our logic, it is missing some required data fields. Is there some other tool or S57 chart viewer that you may have which can validate this update (.033)? I would of course be happy to share technical details of my findings with the HO responsible.

Thanks
Dave

[sailorF54]

Originally Posted by nohal

Bram...
It is not exactly always a good idea to mix the official packages, that install correctly to /usr with this package that installs to /usr/local.
The best probably would be to build even these beta packages with the standard /usr installation prefix, which is done by configuring using

cmake -DCMAKE_INSTALL_PREFIX=/usr ..

before building the package.

For the tidal data missing, the explanation probably is you have opencpn-tcdata from the normal PPA installed in /usr (=the files are in /usr/share/opencpn), while the beta package from Francois, even though happy with satisfied dependency, is looking for them in /usr/local/share/opencpn

Pavel

Pavel
Thanks A LOT for sharing your expertise

Francois

[verkerkbr]

Originally Posted by nohal

Bram...
It is not exactly always a good idea to mix the official packages, that install correctly to /usr with this package that installs to /usr/local.
The best probably would be to build even these beta packages with the standard /usr installation prefix, which is done by configuring using

cmake -DCMAKE_INSTALL_PREFIX=/usr ..

before building the package.

For the tidal data missing, the explanation probably is you have opencpn-tcdata from the normal PPA installed in /usr (=the files are in /usr/share/opencpn), while the beta package from Francois, even though happy with satisfied dependency, is looking for them in /usr/local/share/opencpn

Pavel

Hi Pavel,

i have looked in the folders and that is the cause. The Tidal info is in another folder. Bit strange that the old ones disappear with a "cleaning operation" (sudo apt autoremove).

Thanks for you info.

Regards,

Bram

[Hakan]

About anchorage information:
Win10 Git code as of today.

The "A-key" or Menu "show anchoring info" has restricted functionality.

At Display category:
- Standard: A key is not working.
- All: A key is working.
- Mariner's standard (Select All): A key needs two to three press to switch off when on. One press switch on when off. Repeatable.

Håkan

[nohal]

Originally Posted by verkerkbr

Hi Pavel,

i have looked in the folders and that is the cause. The Tidal info is in another folder. Bit strange that the old ones disappear with a "cleaning operation" (sudo apt autoremove).

Thanks for you info.

Regards,

Bram

Bram...
I think it might be because the dependencies are not correctly included in the locally generated packages, so once you uninstalled the PPA version of the opencpn package and replaced it with the beta one, not build on Launchpad using https://github.com/nohal/launchpad/b...debian/control the dependency might have been lost and opencpn-tcdata was considered an orphan. It should be pulled back in once you install the opencpn package from the PPA.

Pavel

[rgleason]

Originally Posted by Hakan

About anchorage information:
Win10 Git code as of today.

The "A-key" or Menu "show anchoring info" has restricted functionality.

At Display category:
- Standard: A key is not working.
- All: A key is working.
- Mariner's standard (Select All): A key needs two to three press to switch off when on. One press switch on when off. Repeatable.

Håkan

I've noticed this too. I thought it was intended only to work on Mariner's Standard, .... but I guess I was wrong.

[bdbcat]

Hakan/Rick...

I corrected the function of "A" toggle in Mariners Standard mode. In github now.

Now, the function only works in "ALL" and "Mariners Standard" modes. Anchor features are always visible in "Standard" mode. I think we decided this some time back, as a required safety issue. But we can talk about it again, if necessary...

Thanks
Dave

[Hakan]

Originally Posted by bdbcat

Hakan/Rick...

I corrected the function of "A" toggle in Mariners Standard mode. In github now.

Now, the function only works in "ALL" and "Mariners Standard" modes. Anchor features are always visible in "Standard" mode. I think we decided this some time back, as a required safety issue. But we can talk about it again, if necessary...

Thanks
Dave

Dave..
Thanks the "A" toggle now works fine in "All" and "Mariners standard" mode but not in "Standard" mode as earlier agreed. For me that old discussion is completed.
BUT..........
There would be some typo somewhere: The anchorage info is not shown in "Standard" mode and consequently can't be switched on by the A-key.
Håkan

[bdbcat]

Hakan...

The anchorage info is not shown in "Standard" mode

Cannot reproduce that.
For me, the Anchorage areas always show in standard.

Any special steps to reproduce?

Thanks
Dave

[Hakan]

Dave..
Win10. No special behavior. When I use Base or Standard -mode no anchor info is shown. If Anchor info is shown in mode ALL it's switched off when I change to Standard mode.
I use oeSENC, S57 and CM93. OpenGl on/off is equal.
Håkan

[bdbcat]

Hakan...

I think oesenc will still have trouble in Standard mode.
But normal S57 and cm93 should work.

Dave

[Hakan]

Dave..
No, it's the same for S57 and CM93.
CM93, yellow bar, is used in the shots below.

BTW, connected or not. Object query don't list any anchorage object. Neither of : e.g. "ACHBRT", "ACHARE", "CBLSUB", "PIPARE", "PIPSOL", "TUNNEL", "SBDARE"
See shot 2 for files used:

Håkan

[rgleason]

Dave, Hakan,
Current Opencpn 4.8.10112 most recent

CM93 & Enc-USCG01 charts
- Vector Charts - Display Type: All and Mariner's
The "A" Anchor works when zoomed in enough.

CM93 & Enc-USCG01 charts
- Vector Charts - Display Type: Base & Standard
The "A" Anchor does not work.

Is this as expected?

PS: When setting up chart pathnames in the Chart Tab, I noticed some "Tab" studdering. By that I mean I would pick a subdirectory for a set of USCG files and the entire tab would switch from chart files to chart downloader, etc.

[bdbcat]

Rick...

It is understood and correct that the "A" toggle does not work in standard mode.
But the question is: Do Anchorage Areas show in Standard Mode, as they always should?

Thanks
Dave

[bdbcat]

Hakan/Rick...

Here is the deal:
This is the list of Fetures that we consider to be "Anchor-related".

{ "ACHBRT", "ACHARE", "CBLSUB", "PIPARE", "PIPSOL", "TUNNEL", "SBDARE" }

The "anchor-related" Features you see in "ALL" mode (in the screenshots, this is CBLSUB) are specified by S52 to appear only in category ALL, and not in STANDARD. Same for PIPSOL, TUNNEL, and SBDARE.
So, they are never seen in STANDARD.

However, the Features ACHARE, ACHBRT, and PIPARE are specified for STANDARD mode, so we see them if they are present.

In no case does "A" toggle change anything in STANDARD mode.

So, put another way:
In STANDARD mode, we see what S52 requires.
In ALL mode, the "A" is simply a convenience function to clear the screen a bit.

By the way, if we stick closely to the above logic and stay consistent, then the "L" lights toggle should not work in STANDARD mode.

Summary:
I think it is working as intended.

Thanks
Dave