-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to use SVGKLayeredImageView? #5
Comments
Seems the
But
I just updated to Xamarin 15.5-beta and changes to BTOUCH |
Till I look at it to see what the issue is, you can use the Image property to assign your
|
Thank you, Robert!
This way it’s crashing for me.
Alex
… On Oct 13, 2017, at 03:49, Robert N. ***@***.***> wrote:
@alexsorokoletov
Till I look at it to see what the issue is, you can use the Image property to assign your SVGKImage:
var x = new SVGKLayeredImageView
{
Image = new SVGKImage("Media/Sushi.svg")
};
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
@alexsorokoletov Try nuget version I wrote a partial I wrote a quick test to invert the layer colors to make sure that the SVG layers are being created, etc..
Seems to work fine, but not sure the about how to properly size/scale a SVGKLayeredImageView vs SVGKFastImageView/SVGImageView... |
@alexsorokoletov Have you been able to try the new version? |
No, not yet. I will test it next week and let you know. |
@sushihangover new update looks good, but for some reason it broke my build.
For now I rolled back to 1.0.3 |
@alexsorokoletov Using Xcode 8? |
Hmm, most probably XCode 9. Let me check what is on the CI server |
Indeed XCode 8 on the CI @sushihangover |
I think we can close that issue. Method is available in C#, when we update CI to XCode 9, I will update the app. Thank you, @sushihangover |
Hi!
Thank you for this binding and NuGet package!
I wonder, how do I use SVGKLayeredImageView in this binding?
Seems like initWithImage method is missing in the C# surface.
Please advise.
The text was updated successfully, but these errors were encountered: