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
I think the behavior is expected. Can you take a look at the Xaml Controls gallery app in the Windows Store?
sakshi173
changed the title
Gallery][Skia.Gtk/Wasm]Infobadge- Type InfoBadge integer value greater than 999, it always shows default value as 999
[Gallery][Skia.Gtk/Wasm]Infobadge- Type InfoBadge integer value greater than 999, it always shows default value as 999
May 19, 2023
Currently, we're setting a max value of 999 on the Numeric value NumberBox
In the WinUI 2 Gallery, they only set the min value of -1
If I remove the max value, the box has the same behavior as in WinUI 2 Gallery, where the max int value of 2147483647 is accepted and any value higher is ignored (the NumberBox Value field is no longer automatically overwritten when out of range)
Should I go ahead and remove the Maximum NumberBox property as a fix?
@silviuo This would mean that there's a change that was introduced in that control since the import that was made. Can you take a look and see if that 999 value was changed in the original source?
@silviuo This would mean that there's a change that was introduced in that control since the import that was made. Can you take a look and see if that 999 value was changed in the original source?
It came as part of this design improvement commit 3cb7807
Line 126
Current behavior
Uno.Gallery.-.Google.Chrome.2023-05-18.21-58-42.mp4
Expected behavior
The positive integer should display the typed value.
How to reproduce it (as minimally and precisely as possible)
Workaround
No response
Works on UWP/WinUI
None
Environment
No response
NuGet package version(s)
No response
Affected platforms
WebAssembly, Android, iOS, Skia (GTK on Linux/macOS/Windows)
IDE
No response
IDE version
No response
Relevant plugins
No response
Anything else we need to know?
No response
The text was updated successfully, but these errors were encountered: