<gauge:Range StartValue="0" EndValue="2200" Color="Green"> <OnPlatform x:TypeArguments="Thickness"> <OnPlatform.iOS>25OnPlatform.iOS> <OnPlatform.Android>50OnPlatform.Android> <OnPlatform.WinPhone>25OnPlatform.WinPhone> OnPlatform> gauge:Range>
XAML: RimThickness: <gauge:Scale.RimThickness> <OnPlatform x:TypeArguments="x:Double" iOS="40" Android="60" WinPhone="60" /> </gauge:Scale.RimThickness> RangePointer Thickness: <gauge:RangePointer Value="2200" Color="Green"> <gauge:RangePointer.Thickness> <OnPlatform x:TypeArguments="x:Double" iOS="40" Android="60" WinPhone="60" /> </gauge:RangePointer.Thickness> </gauge:RangePointer> </gauge:Scale.Pointers> |
XAML: <gauge:Header.ForegroundColor> <OnPlatform x:TypeArguments="Color" iOS="Gray" Android="Gray" WinPhone="Gray" /> </gauge:Header.ForegroundColor> </gauge:Header> </gauge:SfCircularGauge.Headers> |
Hi Ken,
Sorry for the inconvenience caused.
Regarding Android cropping issue:
We have analyzed the provided sample and found that the RimThickness of gauge is lesser than the circular gauge RangeThickness. Based on the implementation of SfCircularGauge, CircularGauge is start rendering respected to its Gauge Rim in Xamarin (Android). When the Circular gauge RangeThickness is more than the RimThickness, range will render on the gauge rim and it makes the gauge cropping at the edges. It can be resolved by set the thickness for rim or setting offset (0-1) for range. Please refer the following code snippet.
Xaml:
|
Even though we consider this CircularGauge Range cropping and we have created an incident for this. Please have follow up with the incident.
Regarding iOS header issue:
We are able to reproduce the mentioned issue with Circular gauge Headers is not displaying and we have created an incident for the same. Please have follow up with the incident.
Please let us know, if you have any queries.
Regards,
Nijamudeen M.
Hi Helmut,
Sorry for the inconvenience Caused.
Regarding RangePointer behavior:
Based on the implementation SfCircularGauge, RangePointer will overlaps the circular gauge elements such as Range and ticks. So RangePointer rendered properly in Xamarin (Android). We are able to reproduce the mentioned issue with RangePointer rendering in Xamarin (iOS) and we have confirmed this as bug and logged a report on this. Also we have created a support incident under your account to track the status of this issue.
Please log on to our support website to check for further updates.
https://www.syncfusion.com/account/login?ReturnUrl=%2fsupport%2fdirecttrac%2fincidents
Regarding Label Offset and Header size:
We have already found the issue With Label offset and header sizes differs in cross platforms. We will fix this issue and the issue fix will be available in our upcoming Service Pack 2 which is expected by the end of this month. We appreciate your patience until then.
Please let us know, if you have any queries.
Regards,
Nijamudeen M.