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
Is your feature request related to a problem? Please describe.
While poking around in the LCDProc/MythTV interface I noticed it has rather expansive support for LEDs that are attached to certain LCDs.
It'd be neat to abstract this out for a more general purpose capability given that on many small form-factor systems like the Pi or other hardware, it is very easy to have LEDs attached to GPIO headers, I2C, etc.
Describe the solution you'd like
I'm not entirely sure how this would look as even within the generic Linux SysFS LED interface configurations vary - e.g. GPIO LEDs are either on or off, other types (PWM, I2C) may support brightness values or full RGB data, and on top of that you have things like pattern-triggers for effects.
It may be an exercise to the user to implement this support in their own custom script, resulting in the interface becoming an extra dedicated option in the system event configuration, or a property of the LCD configuration to redirect LED handling to a script or binary instead of LCDProc. Currently the set[X]LEDs(...) calls are buried in quite a few places and the LCD code already serves as a point where they all end up converging.
Most likely the interface would be similar in that the script is passed a (stringified?) enumeration and state for the user to act on.
Describe alternatives you've considered
It appears this may be possible in an obscure way by implementing a collection of system event scripts, but this seems very tedious to understand which events end where, and not all of the places that call setLED-ish functions seem to have an obvious event hook where they might be captured.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
While poking around in the LCDProc/MythTV interface I noticed it has rather expansive support for LEDs that are attached to certain LCDs.
It'd be neat to abstract this out for a more general purpose capability given that on many small form-factor systems like the Pi or other hardware, it is very easy to have LEDs attached to GPIO headers, I2C, etc.
Describe the solution you'd like
I'm not entirely sure how this would look as even within the generic Linux SysFS LED interface configurations vary - e.g. GPIO LEDs are either on or off, other types (PWM, I2C) may support brightness values or full RGB data, and on top of that you have things like pattern-triggers for effects.
It may be an exercise to the user to implement this support in their own custom script, resulting in the interface becoming an extra dedicated option in the system event configuration, or a property of the LCD configuration to redirect LED handling to a script or binary instead of LCDProc. Currently the
set[X]LEDs(...)
calls are buried in quite a few places and the LCD code already serves as a point where they all end up converging.Most likely the interface would be similar in that the script is passed a (stringified?) enumeration and state for the user to act on.
Describe alternatives you've considered
It appears this may be possible in an obscure way by implementing a collection of system event scripts, but this seems very tedious to understand which events end where, and not all of the places that call setLED-ish functions seem to have an obvious event hook where they might be captured.
The text was updated successfully, but these errors were encountered: