Does Syncfusion Xamarin.Android tools work for WearOs?

Question

I am trying to build a wearOs app using SfNumericUpDown but it seems to be not working for Xamarin.Android WearOs app. Are they not supported?

Jeya Kasipandi · Answer

Hi Emil,Greetings from Syncfusion.Currently, we don't have support for WearOs. Please let us know if you have any other queries.Regards,Jeya K

Emil · Answer

Hi Jeya,However I tried SfNumericupdown on WearOs, it seems to be working fine for me. Thanks,Emil

Suganya Sethuraman · Answer

Hi Emil,We are glad that the NumericUpDown got working in WearOS. We have not provided support for WearOS for our controls. Since the NumericUpDown is built with Android's TextBox and Buttons with the simple UI it may got worked without any additional implementation.Regards,Suganya Sethuraman

Emil · Answer

Hi Suganya,I would like to ask here something. Although you said that you dont support WearOs, i found that many of the tools are working fine in wearos. I think in general WearOs inherits same controls from Android Mobile. However here I found a small issue with SfNumeric in WearOs. this is probably easily fixable. So basically I have set NumericUpdown.ParsingMode = ParsingMode.Double;This works fine but when the Keyboard on Wear Watch pops up, It displays only numbers but not decimal separator. I believe this is because SfNumericUpdown inherits from either Editor or EditText both have android:inputType="numberDecimal" property. Setting this causes Keyboard to display decimal separator dot or comman. Is it possible to have fix for this if I create a ticket? :)I have tested with       <EditText    ndroid:inputType="numberDecimal" /> works perfectly fine. Please let me know if it is feasible.best

Eswaran Thirugnanasambandam · Answer

We checked the reported problem in the Xamarin.Android platform, and the decimal separator is visible when using NumericUpDown control with and without input type property. As we mentioned earlier, we do not provide WearOS support for Syncfusion controls, hence we are not ensure this with the WearOS.