Replies: 3 comments
-
Maybe we should gather, via github code, a master "commonname" list for all existing plugins. |
Beta Was this translation helpful? Give feedback.
-
Not necessary. |
Beta Was this translation helpful? Give feedback.
-
Ok, it was just an idea. The rule is "You must use the Plugin's "CommonName" and not change it." |
Beta Was this translation helpful? Give feedback.
-
I've learned it is essential to stick with the original "common name" for the plugin and never change it!
Mistakenly changing the "commonname" causes the following issues:
One final note. If for some unknown reason, the "commonname" being used publicly in the catalog has changed and has been used that way for a long time, it is best to change the "commonname" in the code, but only in that situation. It causes less disruption and confusion to users, and PIM works much better.
(unless it has somehow mistakenly changed and is being actively used by Opencpn and is public)
Beta Was this translation helpful? Give feedback.
All reactions