Chart buttons missing from bottom of window

[bdbcat]

Hubert...

Noted.

So what do you need to add/change in ini configuration to make this effect then happen?

S63: Odd...
What does the logfile say about S63?

Thanks
Dave

[bcn]

Re. S-63: Clip of the log attached.

The settings to find the culprit for the "piano killer" will be investigated later....

Hubert

[fgd3]

I wasn't able to reproduce the problem, either. I thought it might have something to do with starting OpenCPN with a window that wasn't maximized, but that didn't seem to make any difference. Do you have quilting enabled? Does that make any difference? Does this work with raster charts, vector charts, or both?

Fabbian

[bcn]

Originally Posted by bdbcat

S63: Odd...
What does the logfile say about S63?

Understood now - my error. Pointing to the complete directory which houses the base charts plus the update folders. Program tried to use the Update folders and not the base first.

And even worse - did not install via the plug-in but just adding a chart-group at "Charts"

[rgleason]

Don't get it. Are you saying that these errors caused the "piano button" problem?
Maybe not.

10:04:12 AM: Searching directory: C:\Charts\Garonne-ECDIS_2.1 for *.s57
10:04:12 AM: Searching directory: C:\Charts\Garonne-ECDIS_2.1 for 00300000.a
10:04:12 AM: Searching directory: C:\Charts\Garonne-ECDIS_2.1 for *.os63
10:04:12 AM: Searching directory: C:\Charts\ES_CW for *.kap
10:04:13 AM: Searching directory: C:\Charts\ES_CW for *.geo
10:04:13 AM: Searching directory: C:\Charts\ES_CW for *.000
10:04:13 AM: Loading chart data for C:\Charts\ES_CW\DC14197ACES_UPDATE_14_24_00.S63\EN C_ROOT\ES\ES30048A\4\0\ES30048A.000
10:04:13 AM: CPL ERROR 1: File `C:\Charts\ES_CW\DC14197ACES_UPDATE_14_24_00.S63\E NC_ROOT\ES\ES30048A\4\0\ES30048A.000' does not appear to have
a valid ISO 8211 header.

10:04:13 AM: s57chart::BuildS57File Unable to open C:\Charts\ES_CW\DC14197ACES_UPDATE_14_24_00.S63\EN C_ROOT\ES\ES30048A\4\0\ES30048A.000
10:04:13 AM: Cannot initialize ENC file C:\Charts\ES_CW\DC14197ACES_UPDATE_14_24_00.S63\EN C_ROOT\ES\ES30048A\4\0\ES30048A.000

[bcn]

Rick,

no, that happened when starting from scratch with no config file and without chart data base.
Re-installing S-63 charts (incorrectly) as stated in my post above of yours. So just forget it....

Still researching.

Hubert

[bcn]

On the Win8.1 PC cleaned the config.ini and started to play with settings and just one chart directory.
Bug does not appear.

Adding the rest (re-installing)
- RNCs (US)
- CM93
- IENC (France)
- S-63 (Spain & AUS)
Bug does not appear

Cloning the settings one by one from the Win7 PC
Bug does not appear

Tried even with COM settings and ownship icon, but no.
So now we have here one PC with and one without.
Mistery..

Hubert

[bcn]

Fiddling with the plug-ins. Forgot that those are different between the two installations.

And it shows up that disabling/enabling the Dashboard does trigger a difference.

The bug shows up only with the Dashboard enabled.

Hubert

[RhythmDoctor]

Originally Posted by bcn

Fiddling with the plug-ins. Forgot that those are different between the two installations.

And it shows up that disabling/enabling the Dashboard does trigger a difference.

The bug shows up only with the Dashboard enabled.

Hubert

I have slightly different behavior. I have Dashboard enabled on some of my PCs (Win8 tablets), but not on others (Win7 desktops). I have seen the problem on all my machines, and just confirmed that enabling/disabling the the dashboard plugin on the machine that I'm using right now does not change the behavior. My piano buttons are gone upon launching both with and without the dashboard enabled.

BUT.........

When I remove dashboard_pi.dll from the plugins directory and launch O, the bug goes away - I have piano keys!!

So in my case, I have the bug whenever the dashboard_pi.dll is in the plugins directory, but not when it's removed.

[bcn]

From your screenshots I see that you are on 3.3.1303 .
Is that still correct?

What happens if you upgrade?

Hubert

[RhythmDoctor]

Originally Posted by bcn

From your screenshots I see that you are on 3.3.1303 .
Is that still correct?

No, those screenshots were done last April. I have duplicated the behavior on every version I've used including 3.3.1606 and 3.3.2302.

There's no need to redo the screenshots when I keep getting the same results.

I think the fact that the bug depends on the presence of the dashboard_pi.dll file in the plugins folder is significant.

[RhythmDoctor]

Originally Posted by RhythmDoctor

I have slightly different behavior. I have Dashboard enabled on some of my PCs (Win8 tablets), but not on others (Win7 desktops). I have seen the problem on all my machines, and just confirmed that enabling/disabling the the dashboard plugin on the machine that I'm using right now does not change the behavior...

I need to correct this statement. I was not disabling the plugin before. I was just hiding the display. Going into plugin settings and clicking Disable does restore proper display of the piano buttons upon relaunching O.

[RhythmDoctor]

Originally Posted by bcn

Dave....

with a virgin config.ini and Chartlist.dat the behavior is correct, not the one we have observed.

Hubert,

After you started over with virgin config.ini and chartlist.dat, did you go in and enable the Dashboard plugin? That's very important, based on what I just saw:

Using 3.3.2302, I deleted opencpn.ini and chartlist.dat, then launched the program. I established one chart directory with NOAA RNC charts (no ENC), and I unchecked the box to display the status bar. After quitting and restarting, piano buttons appeared properly.

But then I went back into settings and enabled the Dashboard plugin. Then after quitting and restarting O, the piano buttons were gone! Note that this was using the virgin opencpn.ini and chartlist.dat files.

So it appears that for me enabling the Dashboard plugin is definitely causing this problem. Try activating Dashboard in your software and see if the bug reappears.

[bcn]

Yes, it boils down just to enable/disable the Dashboard plug-in.
With PI enabled you can provoke the behavior, disabled all is ok.

Viewing back the from-the-scratch install was unnecessary, but helped to keep track between the differences of the two two installs.
Chasing bugs at corners where they not are.......

[bdbcat]

Guys...

Thanks for the research. Now I can make it fail, too

As is often the case, once the bug is isolated and reproducible, a solution is trivial.

Coming for next Beta.

Dave