-
Notifications
You must be signed in to change notification settings - Fork 27
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
ProgressBar bug #37
Comments
Testing XAML: <controls:NumericUpDown x:Name="SliderValue" DecimalPlaces="0" Increment="1" Value="50" /> |
This testing xaml is for NumericUpDown instead of ProgressBar. |
|
|
Testing XAML: <ProgressBar Value="{Binding ElementName=ProgressValue, Path=Value}" Height="20" Margin="0,5" /> this XAML works: |
|
Should be fixed. Please retry. |
Number 3 is still not fixed, still need to set Binding mode = TwoWay. All others are working as expected. |
Fixed binding. Coercing of Maximum and Value in RangeBase was clearing the binding expression. Pushed nuget package 0.9.8.8. |
Progress Bar control missing Default Style. When using DefaultTheme, I can only see a blank box without Progress value. using MetroTheme, I can see the value.
Setting Width on the ProgressBar make the Progress to show 100% regardless the current Value.
Binding only works when set Mode=TwoWay, We should only need one way binding for ProgressBar as the control is a readonly control.
Got "0x800a139e - JavaScript runtime error: Exception: UpdateLayout has entered infinite loop and has been aborted." error when setting ProgressBar value 100. This error can be seen on the demo page when using Metro Style, and setting 100 on the numericbox:
http://faydedemo.azurewebsites.net/default.html#Slider
The text was updated successfully, but these errors were encountered: