Skip to content

Conversation

@yagarwal1307
Copy link
Collaborator

No description provided.

@yagarwal1307 yagarwal1307 requested a review from a team as a code owner September 4, 2025 13:30
@github-actions
Copy link

github-actions bot commented Sep 4, 2025

🚀 Checkout Instructions

To test this PR locally, use one of these methods:

Option 1: GitHub CLI (Recommended)

gh pr checkout 1153

Option 2: Direct checkout

git fetch origin ya/handle-button-events
git checkout ya/handle-button-events

@aisraelov
Copy link
Member

Why not re-use our existing button event infra? The cloud is already set up for that, at least I think?

@yagarwal1307
Copy link
Collaborator Author

@aisraelov
The reason I didn't do that was because it seemed to have defined some enums which aren't true for the nex glasses.
So I wasn't sure if something would break in the chain if I do that.
But you are right maybe we should modify and use the same infra.
Let me look into it again.

export interface ButtonPress extends BaseMessage {
  type: GlassesToCloudMessageType.BUTTON_PRESS;
  buttonId: string;
  pressType: 'short' | 'long';
}

In nex we have 4 different press types for example

cc: @nic-olo

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