-
Notifications
You must be signed in to change notification settings - Fork 45
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
Missing methods to WatchFace binding #703
Comments
Thanks for the feedback and repro sample! Appreciated.
Could be, but without diving in I cannot be 100% sure.
Thanks. Time saver. |
Hello, For information, I just tried with the new version 1.1.1 and still the same problem. Thanks! |
Hello @moljac, Have you had time to dive in? Don't hesitate to ask me if you need to do some tests on a physical WearOs watch if you don't have one. Have a nice day ! |
Hello, Thanks ! |
I was able to reproduce. Now digging in the bindings to see why API was not surfaced. |
Seem that it hasn't been resolved yet... Any updates? |
It does appear these methods are getting removed due to the missing
The good news is we added The bad news is we can't create |
Android application type
Android for .NET (net6.0-android, etc.)
Affected platform version
.net 7 android
Description
Hello,
I just tested the binding of the WatchFace lib.
Unfortunately, some methods are missing like the "render" or "renderHighlightLayer" of the "Renderer.CanvasRenderer" : https://developer.android.com/reference/kotlin/androidx/wear/watchface/Renderer.CanvasRenderer#render(android.graphics.Canvas,android.graphics.Rect,java.time.ZonedDateTime)
Is it related to the "java.time.ZonedDateTime"?
I attach a mini sample.
Thank you,
Pierre
Steps to Reproduce
Create a new project, add nuget "Xamarin.AndroidX.Wear.WatchFace".
Create a "CustomCanvasRenderer" inherit "Renderer.CanvasRenderer".
To be able to create a WatchFace, you need the render() method and renderHighlightLayer(). They are not present in OVERRIDE, nor in the "Renderer.CanvasRenderer" class.
Sample.WearOS.zip
Did you find any workaround?
No workaround.
Relevant log output
No response
The text was updated successfully, but these errors were encountered: