Checkbox (in place of Switch) taking up full width in horizontal layout

Question

I've just started using SyncFusion for Xamarin so excuse my ignorance if this is an easy answer ..

I have an existing app with a horizontal stack layout with fields left to right .. i.e. Switch / Time / Switch / Switch / Text and I want to replace the Switch with an SfCheckbox but when I do the checkbox appears to fill the remaining space so I end up with something like Switch / Time / SfCheckbox ............ with that checkbox taking up remaining room whereas using a Switch doesn't. See screenshots below ...

I've tried setting the HorizontalOptions to not fill but it doesn't seem to have any effect and I'm suspecting it's the text for the label of the checkbox that's causing the issue but don't know.

Any clues as to how to fix this?

Thanks Derek

Paul Anderson S · Answer

Hi Derek, 
  
Greetings from Syncfusion. 
  
We have tried to replicate your reported scenario and we are unable to reproduce the problem in our side. Could you please share some more details such as which version of Xamarin.Forms and SfCheckBox control and which HorizontalOptions, VerticalOptions are used in your sample. It would be helpful for us to give assistance on your problem.  
 
Regards, 
Paul Anderson

Derek · Answer

Hi Paul,Yes apologies for lack of info in this post, after further checking on my side I realised it wasn't exactly as described and in fact have added a second post that explains the situation in more detail and also includes some .XML showing the issue which seems to be related to SfCheckbox not responding to Width="AUTO".Here's a link to my second, more detailed post that hopefully you can help with.https://www.syncfusion.com/forums/140336/sfcheckbox-not-obeying-width-quotautoquot-in-grid-is-this-a-bugBest regards,Derek

Paul Anderson S · Answer

Hi Derek, 
  
Greetings from Syncfusion. 
  
We are able to reproduce the reported issue with SfCheckBox control taking full width and we have logged defect report for the same. We will fix the issue and will be included in our upcoming Volume 3 SP1 release which will be in the end of this month.[October 2018] 
  
Regards, 
Paul Anderson