Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Review name argument vs meta name overload #205

Open
dromer opened this issue Oct 13, 2024 · 0 comments
Open

Review name argument vs meta name overload #205

dromer opened this issue Oct 13, 2024 · 0 comments
Labels
invalid This doesn't seem right

Comments

@dromer
Copy link
Collaborator

dromer commented Oct 13, 2024

Early on in the meta.json I added a method to be able to set the name via the json file, however this also causes a bit of inconsistencies and possibly confusion.

We should review if this overload really makes sense or just stick to the regular method of supplying the project name (used internally for symbols etc.)

For DPF we may want to add a new optional "prettyname" which is used for presenting in DISTRHO_PLUGIN_NAME and is allowed to have spaces and other "pretty" formatting.

@dromer dromer added the invalid This doesn't seem right label Oct 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid This doesn't seem right
Development

No branches or pull requests

1 participant