Skip to content

Conversation

@pastaq
Copy link
Contributor

@pastaq pastaq commented Sep 10, 2025

- Apply similar changes as #432 to improve the OrangePi NEO in the same
  way.
OutputCapability::LED(LED::Color),
];
/// List of all output capabilities that the OrangePi NEO supports
pub const OUTPUT_CAPABILITIES: &[OutputCapability] = &[OutputCapability::ForceFeedback];
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does the OrangePi Neo not support LEDs?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It has RGB that is only controlled through button combo's on the device. OrangePi did not want to spend the money for an API for the MCU.

Comment on lines +251 to +255
// The touchpad doesn't have a force sensor. The deck target wont produce a "click"
// event in desktop or lizard mode without a force value. Simulate a 1/4 press to work
// around this.
let event = Event::Trigger(TriggerEvent::PadForce(TriggerInput { value: 0 }));
events.push(event);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of emulating the touch force in the source device, can we instead handle this in the target device(s)?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd rather not manage source device edge cases in target devices.

@hphilm
Copy link
Contributor

hphilm commented Oct 21, 2025

@pastaq I didn't saw any regressions when I tested it on the Neo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants