I'm posting here the copy-pasted answer from your support ticket on the same topic for anyone else that comes upon this forum post.
supports setting different culture than the default one. You can easily set it to Spanish like this for example (let's say that the x:Name of the indicator is indicator in Xaml):
.indicator.Language = XmlLanguage.GetLanguage(
This will apply comma as separator to your 66
value in case you are using FontNumberPosition
class to represent the appearance of characters in your numeric indicator. This will change the dot to comma separator automatically as the FontNumericPosition shows characters using regular fonts and they support localization.
When using the HexagonalNumberPosition
class however the approach is more complex. You pointed very correctly that we use TemplateSelector class to pick from a predefined number of templates the one that will represent the Hex number (x:Key = HexagonalSevenSegs0,HexagonalSevenSegs1 and etc. ), the Hex dot (x:Key = HexagonalSevenSegs. ) , the Hex comma (x:Key = HexagonalSevenSegs, ) or Hex dash (x:Key = HexagonalSevenSegs- ). And here comes the problem -- our comma data template is practically same as the one that represents dot and even though you might expect to see comma you will see dot instead. We apologize for this issue and will fix it for one of our upcoming latest internal builds.
Till we fix the issue you might choose from two workaround approaches:
1. Use FontNumberPosition only for the comma symbol:
2. I attached a custom project that demonstrates how you might create a custom HexagonalNumberPosition class where the ContentTemplate is your custom one.
Let me know how these suggestions work for you.
P.S. Please mind that we highly reccomend support threads over forums as the response time there is 24h and not 72h.
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Feedback Portal
and vote to affect the priority of the items