You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Same idea as #941, we have some tech debt in the SOCD slider being half in an addon, half in core, and that is confusing to people because they map the pins in the Pin Mapping page and think they're done, without realizing they need to enable the addon, and on the flip side the addon doesn't really do anything all that special other than manage a setting.
#941 set the precedent of having an "active" DP mode, and the same idea would apply here; basically rinse and repeat:
Create an activeSOCDCleanerMode in the core gamepad
Move the mapping of the pins from the addon to core
Have the active mode default to whatever is in the gamepad config, unless one of the mapped pins for the other modes is active
Use the active mode in the core gamepad checks, rather than what is in the config
Remove the addon from the firmware and webconfig
Point DDI and Display code (and maybe more?) at getActiveSOCDCleanerMode()
The text was updated successfully, but these errors were encountered:
Same idea as #941, we have some tech debt in the SOCD slider being half in an addon, half in core, and that is confusing to people because they map the pins in the Pin Mapping page and think they're done, without realizing they need to enable the addon, and on the flip side the addon doesn't really do anything all that special other than manage a setting.
#941 set the precedent of having an "active" DP mode, and the same idea would apply here; basically rinse and repeat:
activeSOCDCleanerMode
in the core gamepadgetActiveSOCDCleanerMode()
The text was updated successfully, but these errors were encountered: