Describe the bug
A DatePickerFlyout whose Date is two-way bound will update target-to-source but not source-to-target.
The following link refers to the same bug and provides a simple (outdated) example project: https://social.msdn.microsoft.com/Forums/windowsapps/en-US/240718c8-a5ee-4528-a748-0d6511401dcf
Steps to reproduce the bug
Expected behavior
Visible date should reset like it does with DatePicker or TimePickerFlyout.
Screenshots
-/-
Version Info
Microsoft.UI.Xaml 2.0.181018003.1
Windows 10 version:
Device form factor:
That's frustrating that you weren't getting traction on UserVoice. We'll take a look at this. I've filed an internal issue and we'll report back.
Whoo-hoo finally! I had already given up a little bit...
My LOB application uses its own date control, which is based on this flyout. Unfortunately there are a lof of use cases where the users are confronted with this failure. We have to record a date and time for the documentation process for almost all datasets...
Thanks for reporting this issue. I have made a fix in the OS to resolve this issue. It will be available in a future version of Windows.
Most helpful comment
Thanks for reporting this issue. I have made a fix in the OS to resolve this issue. It will be available in a future version of Windows.