Gauge challenges after updating to Xamarin 1.3 and Syncfusion 12.4.0.25

[Steen Steiniche]

Hello Syncfusion

 

After updating to Xamarin 1.3 and Syncfusion 12.4.0.25, we have a few challenges getting your gauge working. We have encountered two issues so far:

 

1) On iOS the usual way of defining a gauge renderer throws an exception

 

We have placed the renderer in the AppDelegate.cs this way:

 

public override bool FinishedLaunching(UIApplication app, NSDictionary options)

{

global::Xamarin.Forms.Forms.Init();

new Syncfusion.SfGauge.XForms.iOS.SfGaugeRenderer();

LoadApplication(new SyncFusionTestBench.App());

 

return base.FinishedLaunching(app, options);

}

 

This throws the error: "System.Exception: Could not create an native instance of the type 'Syncfusion.SfGauge.iOS.SFCircularScale': the native class hasn't been loaded"

 

 

2) On Windows Phone and iOS, the gauge control takes up the entire vertical space of the device screen.

 

Even when placing the gauge inside a StackLayout with vertical options set to LayoutOptions.Start, the gauge takes up the entire height of the device and places the gauge in the center.

 

We have attached an example project that illustrates the issues. If you look at the result of the Android project, you will see it behaves as we would expect the other two platforms to behave.

 

 

Looking forward to hearing your solution

 

Thanks in advance

Steen

Attachment: SyncFusionTestBench_e0c84a09.zip

[Joy Oyiess Rex K]

Hi Steen,

 

Query #1 - Regarding the issue with Exception in the iOS Gauge renderer

 

Sorry for the inconvenience caused. The mentioned issue might be due to assembly problem. We have already fixed it and refreshed the build in online on the same day itself. So, can you once please uninstall and install the latest build again from our site or component store to solve this.

http://www.syncfusion.com/downloads/xamarin-service-packs

https://components.xamarin.com/view/SyncfusionEssentialStudio

 

Query #2 - Regarding the Gauge control behaviour in the StackLayout

Usually, we will render our CircularGauge control based on parent size since we will not set any default size (minimum size) for our control. In StackLayout case, we didn’t get the proper parent size in Android platform so that only we are setting width/height based on the Stack Layout orientation. If we didn’t considered the height/width like that we will not be rendered.

 

Also, whenever we use the StackLayout the good practice is to set the size of the control. So, please set the height of the Gauge control in your application to avoid this behaviour.

 

Please let us know, if you need any further assistance.

 

Regards,

Joy Oyiess Rex K​

[Steen Steiniche]

Hello Joy

 

Thanks for your reply.

 

Ad reply #1: I used the dlls from the 12.4.0.25 SP and that solved the iOS renderer problem. Thanks for that.

 

Ad reply #2: I disagree with your choice of default size behavior of the gauge control. By default it should not take up the entire screen - it should only do this when using VerticalOptions and HorizontalOptions to that effect. Setting the height (and width) is a workaround, that works, so that's what I have done. But it IS a workaround and an unnecessarily complicated one if you want the gauge to dynamically fit the width of the screen only and not the height.

 

Thanks

[Joy Oyiess Rex K]

Hi Steen,

Thanks for your previous update.

We have analysed the gauge sizing behaviour in stack layout, for that we have logged a report in our database, we will resolve this issue in our upcoming SP release which is expected to be available by the end of Feb, 2015, we appreciate your patience until then. Kindly use the previously mentioned work around to resolve your issue.

Please let us know, if you have any concerns.

Regards,

Joy Oyiess Rex K

[Steen Steiniche]

Hello Joy

As mentioned above, the renderer in iOS now works (query #1). However, the gauge itself has stopped working correctly. It does not update and even seems to block the UI thread. Please see attached example.

Hope to have a solution for this soon.

Thanks

Attachment: SyncFusionTestBenchSP_2506c90f.zip

[Joy Oyiess Rex K]

Hi Steen,

Sorry for the inconvenience caused

We have analysed the mentioned issue in the provided sample, we have logged a report for the same in our database. We will resolve this issue and the issue fix will be included in our upcoming SP release along with the solution for query 2, which is expected to be available by the end of Feb, 2015, we appreciate your patience until then.

Please let us know, if you have any concerns.

Regards,

Joy Oyiess Rex K

 

[Steen Steiniche]

Hello Joy

Thanks for your quick response.

We have planned a release to customers of the app in question by the end of this week. We cannot wait to resolve this to the end of February. 

The gauge control is central to the app and we had it working prior to the updates to support Xamarin 1.3 and iOS unified.

I very much hope and expect Syncfusion to find a way to send us a patch to resolve the issue immediately.

Thanks in advance

[Joy Oyiess Rex K]

Hi Steen,

We will fix the mentioned issue, and it is needed to be tested under various scenarios. If you need custom assemblies for this fix in advance, please create an incident in the below link.

https://www.syncfusion.com/account/login?ReturnUrl=/support/directtrac/incidents/incidents/newincident

We will update you the custom assembly through the created incident on Feb 06, 2015. We appreciate your patience until then.

Please let us know, if you have any concerns.

Regards,

Joy Oyiess Rex K

[Steen Steiniche]

Hello Joy

 

We have not yet received a custom assembly for the gauge error. Please let us know when to expect it.

 

Thanks

Steen

[Joy Oyiess Rex K]

Hi Steen,

 

Sorry for the inconvenience caused.

 

As mentioned in our previous update, custom assemblies/patch can be provided only through the incidents (not through the forums). We have created an incident # 135081 for the same and updated the custom assemblies in it, please follow up on the same incident regarding this query.

 

Please let us know, if you need any further assistance.

 

Regards,

Joy Oyiess Rex K