-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
WinUI TimePicker needs to expose additional properties #16095
Comments
What is the handler that you have tried? Did this work in .NET 7? |
Hi @Stedy59. We have added the "s/needs-info" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time. |
I will create a repo that include my custom Handler/Mapper. Please look at this... |
This has never worked properly on any version I have used. Here is a repo of the Android/WinUI "TimePicker" handler I mentioned earlier... Thank you for all you do! |
Verified this on Visual Studio Enterprise 17.7.0 Preview 6.0. Repro on Windows 11 .NET 8 with below Project: |
Description
The time selection popup portion of the control does not inherit any Font properties, [Family, Size, Color]
Also, there is no property exposed to allow the selected time background color change. I also attempted to modify the base control's resource dictionary. but none of the popup value "keys" responded to change.
Steps to Reproduce
Create a .net Maui app
Add a TimePicker to the view
Link to public reproduction project repository
n/a - just create a new project
Version with bug
8.0.0-preview.5.8529
Last version that worked well
Unknown/Other
Affected platforms
Windows
Affected platform versions
Windows SDK - all
Did you find any workaround?
no - as stated, even creating a handler, the WinUI control seemed to ignore the changes!
Relevant log output
No response
The text was updated successfully, but these errors were encountered: