[FEATURE] Add command-line option to specify a custom configuration file
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start with the configuration-file behavior described in the README at lines 94-101, then locate how projectMSDL.properties is found, loaded, and saved. Determine the command-line option and define how an explicitly supplied file interacts with in-app saving. Done means the standalone SDL2 frontend accepts a custom configuration path and handles saving to the intended file.
Written by the indexing model from the issue text.
Description
Please confirm the following points:
- This feature request is NOT for the Android apps in the Play Store
- I have searched the project page to check if a similar request was already made
Application or Project
projectM Standalone SDL2 Frontend (includes the Steam app)
Is Your Enhancement Related to a Problem?
projectMSDL.properties is created in a specific directory, but there is no command line option to override it.
https://github.com/projectM-visualizer/frontend-sdl-cpp/blob/master/README.md?plain=1#L94-L101
Your Suggested Enhancement
Add a command line option to specify a projectMSDL.properties file. Since there is a save option inside the projectMSDL app, may need to check if a config file was passed in, and make a decision whether changes should be saved to the currently loaded file. Perhaps the user could be provided the context of what save file is currently loaded.
I think also maybe copying the default file with the helpful commented out setting descriptions to the user file might be helpful.
Alternative Solutions
No response
Additional Context
No response
- Dominant language
- C++
- Stars
- 116
- Forks
- 64
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from projectM-visualizer/frontend-sdl-cpp
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
projectM-visualizer/frontend-sdl-cpp#134 · 4 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
A delete command to remove visualizations that are buggy, don't work, or are just not good looking. Openenhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
projectM-visualizer/frontend-sdl-cpp#120 · 1 comment ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
projectM-visualizer/frontend-sdl-cpp#118 · 2 comments ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 28/100
projectM-visualizer/frontend-sdl-cpp#110 · 6 comments ·
All issues in projectM-visualizer/frontend-sdl-cpp
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
NVIDIA/cuda-samples#453 ·