User Profile & Activity

Arief Handany Member
Page
of 20
Posted: August 14, 2015 4:36 AM

Hi Thomas,

Sorry im very late to inform you, yes we did test it and actually i'm explain him wrong, looks like if this is the case i can't make a workaround but i already inform to our developer under code CROS-887

Hope that'll helps

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!

Hi Jimmy 

Nevermind above post, i managed to make it done using source version of Signature Pad, feel free to check it out in attachment!

here is files that i changes in my project:
Android/SignaturePad/SignaturePadBindingAdapter.cs
Android/SignaturePad/MySignaturePad.cs
Android/Resources/Layout/MainLayout.axml
Android/Infrasturcture/AppInitializer.cs

Hope that'll helps!

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?

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 Jimmy,

CROS-858 and CROS-859 already included in our July-August 2015 Sprint but i will update you if there are hotfix or updates.

Posted: July 31, 2015 9:35 AM

Hi Thomas

We are tested it in both Java SDK 1.7 and 1.8, looks like it not caused by rounded button, hmm i think we back to square one.

Hi Jimmy,

We released this as hotfix which you can obtain it here http://git.intersoftpt.com/projects/CROS/repos/updates/browse/Crosslight4_0_5000_290. Hope that'll helps.

Posted: July 30, 2015 1:29 AM
Hi Thomas

I misread your request, i forget that you want to use multiple layout id and the method he gave to me actually using only one layout id.

Will update try to make sample with multiple layout id based on the method
Posted: July 29, 2015 3:03 AM

Hi Thomas,

We are unsuccessfully replicate the problem even using API 19/4.4.2 in our phone, but our programmer got a lead based on your error report.  Looks like it likely caused by the rounded button doesn't inflate but we maybe need to investigate more, 

Could you try this sample, we remove rounded button from main list and put it in one of dialog presenter.

All times are GMT -5. The time now is 8:42 AM.
Previous Next