Gauge having second number position offset

Radzen Studio Blazor Server
1

Hello Everyone,
I'm posting this question because I have a small problem with the Gauge component.
What I'm seeing in my dev solution is the position seems to be very off a lot and this look like it is caused by the position using ',' instead of '.' for the float value. Let me show some snippet/Screenshot

Check the values for my site :

image
image1289×452 25.1 KB

with x : 53,8234xxxxx and y : 165,0170xxxxxx

I did try to change them to 53.8234xxxx and 165.0170xxxx and the number are drawing to the perfect position.

So it's like it's maybe related to the locale of my system (I'm a french person) or I don't know.

Please help me figure it out

Thanks!

2

Hi @striker3131,

This seems to be another culture related issue (floating point numbers being serialized with a comma instead of a dot). We will fix it with the next Radzen.Blazor release. Thank you for the report.