OpenStickCommunity / OpenStickCommunity/GP2040-CE
Allow SOCD settings to be stored alongside a Profile
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.5k
- Forks
- 666
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 7
Description
Please read these quoted sections before submitting, and remove them (including this one) when you have provided what
is asked, in order to make addressing the issue easier for everyone. Thank you!Be sure to:
Problem
Different games have different optimal SOCD resolution (e.g. neutral for SF6, vs SOCD-U for tag fighters). Often times, this warrants changing a profile as well as inputting a shortcut on the device to change SOCD.
Solution
Store SOCD settings alongside a profile. This allows a few improvements:
- Reducing one less device input to change SOCD alongside changing profiles
- Intuitively, this makes it very easy to set-it-and-forget-it for each game
- With the recent 0.7.10 release, custom profile names will benefit displays. Seeing the correct profile on your device display is insurance that your SOCD is set correctly, instead of managing two changes on first-plug.
Do you plan to work on this feature yourself?
Yes. I will create a PR to kick things off, and will engage w/ the community and Discord to get this merged.
Notes
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.
Research direction
The issue does not name files, tests, or entry points. Start by locating profile storage and SOCD resolution handling in the firmware, then determine how each profile should retain and apply its SOCD setting. Done means profile changes also select the intended SOCD behavior without a separate device shortcut.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- embedded-iot
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100