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
This issue is the place of discussion for adding physical keyboard support to the app.
To achieve this, the following steps need to be taken:
Investigate the feasibility of implementing physical keyboard support in the app.
Identify the necessary APIs and resources required for implementation.
Initial research:
Preliminary research suggests that listening to and handling physical keyboard keypress events is possible. This direction needs further exploration.
Next steps:
Conduct a detailed study of the available APIs and resources for handling physical keyboard events.
Evaluate the possible challenges and limitations of implementing physical keyboard support.
Develop a proof-of-concept implementation to validate the feasibility and effectiveness of the chosen approach.
Any suggestions, resources, or insights about implementing physical keyboard support are welcome. Please feel free to contribute to the discussion below.
The text was updated successfully, but these errors were encountered:
We have reviewed your request and have concluded that there is no supported way to achieve the desired functionality given the currently shipping system configurations.
I think it's doable in a very hacky way, but I'm unsure that it'll provide a good user-experience. I'll keep this issue open for now until I try to implement the hacky way and see what the outcome is.
This issue is the place of discussion for adding physical keyboard support to the app.
To achieve this, the following steps need to be taken:
Initial research:
Preliminary research suggests that listening to and handling physical keyboard keypress events is possible. This direction needs further exploration.
Next steps:
Any suggestions, resources, or insights about implementing physical keyboard support are welcome. Please feel free to contribute to the discussion below.
The text was updated successfully, but these errors were encountered: