04-04-2022 13:13 PM
03-may-2022 update: fixed division-by-zero error message showing up from time to times (thanks @cparedes for reporting this)
Based on @davidni's blog article (available here) I created a configurable Circular Progress Bar component.
Here is how it looks:
Here are the properties you can set on the component:
Feel free to use it... If you have any comments or suggestions, please do not hesitate...
You will find the component right here:
Just updated the component to allow two types of display for the value in the center:
So a new property called ValueMode will allow you to choose between those two modes. To set its value, use the enumeration property called ValueModeEnum like this:
ValueMode = MyCircleProgressBar.ValueModeEnum.Progress -or- ValueMode = MyCircleProgressBar.ValueModeEnum.MaxValue
If you choose the ValueModeEnum.Progress value for ValueMode, just know that the calculation of the current progress value will be automatic based on both the Max and the Value property values.
Also, using the PercentageDecimals property, you will be able to decide how many decimals should be displayed in case the value is shown as a percentage.
You Rock! Between this one and the fabric UI icons... Thank you!
Btw... any thoughts of changing your fabric UI component into a fluent UI component?
Mmmm... I have recently seen this error in other cases as well... It looks like some control property values are populated AFTER the execution of the formulas...
Since it's a bit hard to reproduce this error on my side, can you edit the component in your app and change these red portions of code:
And also change this:
If this fixes the issue I will update the component with the fix.
Waiting for your feedback...
Thanks for your quickly response.
Your code Works perfectly!!!
I had already tried to add exactly that part of the code but I needed to validate "IsBlank" because it caused me the same error.
With the validation "IsBlank" the problem has been solved. Only additional I add in the "If" an "else" to set the value of my variable.
Glad it works now... I'll update the component shortly... 😉