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

PhysicalKey handling for Tizen #12992

Open
MrJul opened this issue Sep 22, 2023 · 2 comments
Open

PhysicalKey handling for Tizen #12992

MrJul opened this issue Sep 22, 2023 · 2 comments

Comments

@MrJul
Copy link
Member

MrJul commented Sep 22, 2023

Following #12549, PhysicalKey and KeySymbol should be handled for Tizen physical keyboards.

@OmidID
Copy link
Contributor

OmidID commented Dec 9, 2023

Hello,

I cannot find any property or any option to get the keyboard layout from Tizen. Can you explain please what is the case if OS do not provide this kind of information?

I do not find a way to pass the type of input, I mean RemoteControl or Gamepad. They are counted as keyboard input from Tizen.

Thanks a lot.

@MrJul
Copy link
Member Author

MrJul commented Dec 11, 2023

Well, if the OS doesn't provide it at all, there isn't much we can do.

For VNC, where we don't have keyboard information either, I simply didn't map the PhysicalKey at all (it's always None), but I guess it could make sense to at least map the standard virtual control/function keys (e.g. Enter, Backspace, F1, etc.) to physical keys, as these won't change depending on the layout and the user might expect the property to be set. Tizen could do the same here.

OmidID added a commit to OmidID/Avalonia that referenced this issue Dec 23, 2023
maxkatz6 added a commit that referenced this issue Jan 10, 2024
* Add key device type and implmentation for tizen #12992

* Add device key type to Android

* Resolve comments

---------

Co-authored-by: Max Katz <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants