Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Thomas/arturia keylab mk ii show remote control values #76

Merged

Conversation

bitwig-thomas
Copy link
Contributor

No description provided.

if (parameter.exists().get())
showNotificationOnDisplay(parameter.name(), parameter.displayedValue());
});
layer.bind(mEncoders[i], showNotificationAction);
Copy link
Contributor

Choose a reason for hiding this comment

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

is it possible the hardware control is mapped to something else than the parameter?

Copy link
Contributor

Choose a reason for hiding this comment

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

Also why are we not just binding some text display computer to the current parameter to update the text display?

encoder.isUpdatingTargetValue().markInterested();
encoder.targetName().markInterested();
encoder.targetDisplayedValue().markInterested();
encoder.isBeingTouched().markInterested();
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this line strictly necessary? I don't see any use of the isBeingTouched value anywhere. Or am I just missing it?


private void showNotificationOnDisplay(final StringValue topRowText, final StringValue bottomRowText)
{
final int notificationDurationInMs = 500;
Copy link
Contributor

Choose a reason for hiding this comment

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

One minor change. Maybe we can instead just have a pointer to the ConttinuousHardwareControl that we are adjusting rather than having a top and bottom row text?

@NickJAllen NickJAllen merged commit a45ea22 into api-18 Jan 19, 2024
2 checks passed
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.

2 participants