Hi Domingo,

Thanks for sending out your sample. We understand your difficulties in implementing the BindableProperties, therefore we have attached a sample that might help you to understand and implement your own BindableProperties for the SignaturePad. Since this is a custom view, it might be difficult to use the built-in bindable properties that comes with Crosslight.iOS. We would like to suggest you to create your own binding adapter with your own bindable properties that will help you to achieve your goal elegantly.

Take a look at this sample : https://github.com/IntersoftSolutions/CustomBinding

First of all, I will explain a bit how this sample works. In this sample, I have created a view named UISignaturePadView. Then, the next logical step would be, I have to create the "connection" between my custom label and my custom bindable properties. This is where the binding adapter comes in. By using the binding adapter, and registering the binding adapter in the AppInitializer, this allows you to "connect" your custom view with your bindable properties.also giving you full control during the attach, detach, get, set value of each bindable properties to your custom view. Then in the binding provider, when you add your own AddBinding definition, notice that the Attach and the proper Get-Set event gets triggered in the BindingAdapter lifecycle. In this sample, I'm just creating a simple, custom bindable text property that can be bound to my custom label.

Hi Domingo,

We have updated the sample in the GitHub link below"

https://github.com/IntersoftSolutions/CustomBinding

In this sample, I used the SignaturePad Component. In order to reflect the image to view model, first of all, I use UISignaturePad as a view that subclasses the SignaturePadView component.  Create the ImageProperty in the UISignaturePad. Then, override the TouchesEnded Method from SignaturePad, and set the ImageProperty with latest image. Don't forget to give SetPropertyValue to the ImageProperty setter in order to reflect the ViewModel. The reflected value will be set in the ViewModel.

Thanks,

Nicholas

Hi Jimmy,

Sorry no news for a long time i tried creating the samples for you however i got weird error when linking the assemblies to the Signature Pad (non sources) and already tried to contact other developer, you can see mine in the attachment. Could i see yours maybe i can help you fix it?

As you can see i handle the image getter when MotionEvent is Up and then pass it to bitmap which in turn will be transformed into Byte[], also don't forget you must register your bindingadapter inside your Android -> Infrastructure -> Appinitializer.cs, however i can't get it work because i send me link assemblies error, did you get the same error?

Also just a news for you we will support Signature Pad but maybe not  as a hotfix, however as next version but still version 4, as far as i know the development team already done but i will ask them if you interested.

Hi Arief,

Sorry no news for a long time i tried creating the samples for you however i got weird error when linking the assemblies to the Signature Pad (non sources) and already tried to contact other developer, you can see mine in the attachment. Could i see yours maybe i can help you fix it?

We did the same approach as what was shown on the iOS sample provided by Nicholas, but we are not getting any errors on Android. We did register the binding adapter and all other settings required to make it work. However, we may be missing something because even with the use of Crosslight v4 doesn't seem to help.

Also just a news for you we will support Signature Pad but maybe not as a hotfix, however as next version but still version 4, as far as i know the development team already done but i will ask them if you interested.

But we are very interested in this update as a hotfix if possible. This is really an important piece of our app, especially on field services... which is widely used on the iOS version.

Hi Jimmy

They already done developing Signature Pad but there maybe still reviewing from higher management but it was included with current sprint, so i can't say exactly when it will be released but likely not as a hotfix.

However i will help you for Android Signature Pad, maybe i can ask the development team the right method, maybe you can send us your code (or maybe just Binding Adapter and .cs for the assemblies). Also did you use the source code or assemblies downloaded from Xamarin?

Yeah haha, i really feel it for you when there is no error at all, fortunately i can ask our programmer. 
Also thanks to them i can found solution for my link assemblies error.

Anyway thanks for the kudos Jimmy! i appreciated it very much :)

If you have more question feel free to ask us!