-
Notifications
You must be signed in to change notification settings - Fork 150
[Xamarin.Forms] Setting 'Points' requires the view be visible #93
Comments
The It should accept any collection of Xamarin.Forms |
The problem is that we are trying to load points to Empty SignaturePad. From source code we can see implementation of
If we will look into
As a result, it is possible to load points to Pad in case you have anything on it (handwritten by user before). But if it's empty (so page just opened), you can't... Attaching file with sample points array variable. Try to add SignaturePad control on Page.xaml, then in Page.xaml.cs set the Points property, before any actions will be done from UI. For me |
Thanks for pointing this out. I did some investigation, and I now know where the issue lies, but I am not sure on what the best way to fix it. It is not exactly an issue (but still is), since this is how Xamarin.Forms works. As the We could find some way to temporarily store the points until the view is made visible, but I am waiting on the Forms team for confirmation and suggestions. In the meantime, I would suggest setting the points in the |
Just for reference, I have uploaded a test project that demonstrates the issue: |
@mattleibow, thank you for advice with setting points in the But small suggestion - it will be good to extend examples documentation. In GitHub docs |
In my case, I tried to save the signature.Points. After that I recall it again to load into the pad but it's empty nothing appearing just the pad. I've worked in Xamarin Forms. |
@staunchman Due to the way Xamarin.Forms works, you will have to load the points in the OnAppearing event: #93 (comment) |
hey @mattleibow, thank you for the Workaround. |
Method "LoadPoints()" only available for platform specific implementation, but you can't use it in PCL. Is it in the roadmap/ it is not planned?
Also tried to use "Points" property, but it's setter is dependent from event, which is private. Maybe it is another easier way to load points?
The text was updated successfully, but these errors were encountered: