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
When a MenuItem has a Gesture set to the InputGesture, on Android devices the gesture displays the Key enum string rather than a more userfriendly version. For example "OemPeriod" instead of "."
This is because the PlatformKeyGestureConverter used (at least by the Simple theme) doesn't have a specific Android case, and falls back to KeyGesture.ToString() rather than using it's own methods for more user friendly string creation.
To Reproduce
Add an InputGesture of, for example "Meta+." to a MenuItem and open the menu on Android. Screenshots below.
Windows:
Android:
Expected behavior
Android also displays userfriendly strings rather than Key enum values.
Avalonia version
11.1.0-beta1
OS
Android
Additional context
Pull Request coming soon.
The text was updated successfully, but these errors were encountered:
Describe the bug
When a MenuItem has a Gesture set to the InputGesture, on Android devices the gesture displays the Key enum string rather than a more userfriendly version. For example "OemPeriod" instead of "."
This is because the PlatformKeyGestureConverter used (at least by the Simple theme) doesn't have a specific Android case, and falls back to KeyGesture.ToString() rather than using it's own methods for more user friendly string creation.
To Reproduce
Add an InputGesture of, for example "Meta+." to a MenuItem and open the menu on Android. Screenshots below.
Windows:
![Win11 Screenshot](https://private-user-images.githubusercontent.com/132860927/322672858-f0c68b97-0414-4d12-b45e-b7466080b67f.jpg?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk3NzQwNTAsIm5iZiI6MTczOTc3Mzc1MCwicGF0aCI6Ii8xMzI4NjA5MjcvMzIyNjcyODU4LWYwYzY4Yjk3LTA0MTQtNGQxMi1iNDVlLWI3NDY2MDgwYjY3Zi5qcGc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwMjE3JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDIxN1QwNjI5MTBaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1jNjNkZTZlZGRkYzhiYmFlMGQ3NDcwOTE5ZDljZWY0MTI2NTBiZTdkN2UwMWE4Nzc1Zjc0YWY5NjIzODhlOTA1JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.zcGsKX-OZLjKBL9bEU9c59GLOLHUUfBeZCQSaEGVD_Q)
Android:
![Android Screenshot](https://private-user-images.githubusercontent.com/132860927/322672852-34f3abe3-0f9b-40f5-90bc-7173e0199972.jpg?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk3NzQwNTAsIm5iZiI6MTczOTc3Mzc1MCwicGF0aCI6Ii8xMzI4NjA5MjcvMzIyNjcyODUyLTM0ZjNhYmUzLTBmOWItNDBmNS05MGJjLTcxNzNlMDE5OTk3Mi5qcGc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwMjE3JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDIxN1QwNjI5MTBaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1iN2I0ZGRmODJjNzdiNWNmNTM5NDlkZjY4NWUyZjA0ZGViYWNiYmY5NTk5MDJjYzM0MWQ3YmI4OTQ4OTM2ODlkJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.HlwTJaBVF0tQBdzINo-e1dLg3-WR8-kjQ8yZZMRWDTk)
Expected behavior
Android also displays userfriendly strings rather than Key enum values.
Avalonia version
11.1.0-beta1
OS
Android
Additional context
Pull Request coming soon.
The text was updated successfully, but these errors were encountered: