Chartsymbols.xml

[Schnapsy]

In versions prior to version 5.2 of OpenCPN, the Chartsymbols.xml file included the lines "DASHB", "DASHL", "DASHF", etc., which allow you to modify the appearance of the dashboard (background color, color of labels , etc.).

In version 5.2, these lines are no longer present.

If I want to customize the dashboard, is it better to replace the Chartsymbols.xml file from version 5.2 with a old one, or simply add the missing lines to the Chartsymbols.xml file from version 5.2?
Indeed, in addition to these missing lines, there are other changes in the new Chartsymbols.xml file compared to the old one.

What will be the consequences of simply replacing the new Chartsymbols.xml file with the old one?

[rgleason]

Schnapsy, you've discovered something very interesting that I did not know.

I find this page in the manual is perhaps relevant
Vector Palette


What are some of your favorite Dashboard Instrument looks with DashB, DashL, DashF?

[Schnapsy]

Originally Posted by rgleason

What are some of your favorite Dashboard Instrument looks with DashB, DashL, DashF?

Attached, an example of an extract from the dashboard that I use.
But I also modified some dashboard dlls to get exactly what I want, which is one of the essential qualities of OpenCPN.

But that does not answer my question ...
"What will be the consequences of simply replacing the new Chartsymbols.xml file with the old one?"

[rgleason]

I hope Dave or someone can answer your question. Why not just try it to see what happens? I like your dials.

[Schnapsy]

Originally Posted by rgleason

I hope Dave or someone can answer your question. Why not just try it to see what happens?

I have tried with the previous file and, also, with the new file modified.
All seems working at this time, but...?

Indeed, in addition to these missing lines, there are other changes in the new Chartsymbols.xml file compared to the old one.

[Canne]

Hi Schnapsy, maybe you will find this interesting:

(Set in DashT ini/conf, not in Chartsymbols.xml, respects Day/Dusk/Night).
Petri

[rgleason]

Petri and Canne these are very very useful developments. Is it possible to implement them in a more mainstream way through the plugins preferences settings? Maybe other users could provide additional "style" files for selection in preferences.

[Canne]

Hi Rick, sure, requires a bit project management which is not generally well accepted by the lambda hacker... One needs a) a project-wide style guide for widget elements to obtain unified look and feel, then force the hacker a bit b) in ocpn_plugin.h, instead of

extern "C"  DECL_EXP bool GetGlobalColor(wxString colorName, wxColour *pcolour);

something like

extern DECL_EXP std::unique_ptr<Widget_Colours> GetColours_Plugin( );

providing a pointer to a unified widget color maps. Would be easy to write, instead (for the above)

void DrawNeedleHub( wxGCDC* dc, int cx, int cy, int radius, bool dataAvailable )
{
    wxColour cl;

    if ( dataAvailable )
        GetGlobalColor( g_sDialCentralCircleColor, &cl );
    else
        GetGlobalColor( g_sDialColorIs2, &cl );

like

void DrawNeedleHub( wxGCDC* dc, int cx, int cy, int radius, bool dataAvailable )
{
    wxColour cl;

    if ( dataAvailable )
        cl = *wdg_col_ptr->DialHubEnabled;
    else
        cl = *wdg_col_ptr->DialHubDisabled;

.. or such ..

User would select from themes in OpenCPN preferences; Plug-In Manager would push the selected themes color's to plug-ins which would have unified color world.

Anyway, even my plug-in specific solution respects the OpenCPN color world since it accepts only names defined in chart1.cpp. Not very project-wide approach, but an attempt towards it.

(added: see https://manual.audacityteam.org/man/themes.html another popular wxWidgets app on my computers).

[rgleason]

As is usual, Petri, you are stretching my mind here. You are suggesting it would be possible to have a "Themes" setting in Opencpn preferences that would set the "theme" to be used for all plugins? ..and it would not be build dependent?

That is pretty nice actually, I would love that, and I think many others would too. It might solve the nighttime problem with all plugins and would give more flexibility.

[Canne]

Why not? Project management decides what they want us, plug-in developers to do by providing an API we shall use. A style guide would not hurt. Of course, the biggest job would be in OpenCPN, not on plug-ins. Theme files would have their own syntax, JSON or XML file so that talented users like Schnapsy above could make the community to profit from their artwork without having to compile anything...

[Schnapsy]

Originally Posted by Canne

Hi Schnapsy, maybe you will find this interesting:

(Set in DashT ini/conf, not in Chartsymbols.xml, respects Day/Dusk/Night).
Petri

Hello Petri,

Thank you for this indication which opens up many possibilities.

I will also quietly work on what you explained in post #8 because it is interesting and opens up many perspectives.

[rgleason]

Feature Request: Added to Tracker and github Issues
https://opencpn.org/flyspray/index.p...s&task_id=2700
https://github.com/OpenCPN/OpenCPN/issues/2030