Both for Win32 and Linux
@Gillibald You were using clang 10? Did you notice anything?
@kai_low0n_twitter The way I found is by clipping the canvas using a path or region: https://docs.microsoft.com/en-us/xamarin/xamarin-forms/user-interface/graphics/skiasharp/curves/clipping
In my scenario for an SKCanvasView, clipping is quicker than a full canvas redraw most of the time. However, it can end up being slower if you have enough dirty rects that cover enough area (even if they don't cover the whole canvas).
Perhaps SKGLView clipping is faster though.
Perhaps SKGLView clipping is faster though.
Hi folks, your thoughts and opinions are needed. I am trying to decide if splitting the largish SkiaSharp package is worth it: https://github.com/mono/SkiaSharp/issues/1073#issuecomment-629692839
and this is really a one-time thing. like, the very first time ever.
I’ve worked with a lot of projects that added complexity for what seemed like a good idea at the time, but required radical refactoring or full rewrite in a couple of years because it just became too difficult to keep moving forward. Can’t see the convenience value - unless it affected app file size/download speeds.
Hi folks, not sure if it was someone here or on Twitter that said they didn't like the fact a
For example a
I was thinking if you had any opinions or actual use cases, then just drop a comment here: https://github.com/mono/mono/SkiaSharp#1301
dotnet publish put all the native runtimes in the output folder of the apps...For example a
dotnet publish for a netcoreapp3.0 will put tizen and iosI was thinking if you had any opinions or actual use cases, then just drop a comment here: https://github.com/mono/mono/SkiaSharp#1301
Seems my slack-to-gitter bot is not getting it right again
We are adding more animations and would like to cap the frame rate to reduce the power consumption, especially for mobile this can be important.
Right now, once way is to use a timer.
I need to have a look at how you are supposed to implement this.
@mattleibow @Cheesebaron We will use it for all platforms. We now have a solution where use a timer to invalidate the canvas. It works okay. Not sure how it affects the smoothness of the animation. A simpler solution would be to invalidate the canvas within the render loop while the animation lasts. In that case I would like to cap the frames per second. I was expecting something like that was present, but if it is not it is not a big issue for us.
I would be interested to know how this is implemented in game components. I could calculate the time left until the next frame should start and pause for that duration in the renderloop. Would that be a smart solution? How to pause? Use Thread.Sleep? What would be the best option performance wise?
It will be v2.84.0-pr.1321.xxx on the usual https://aka.ms/skiasharp-eap/index.json
I am doing some more work to make the "set" api much better and be a case of:
var inputs = new SKRuntimeEffectInputs(effect) {
["abc"] = 1f
}
As soon as it is up, i'll ping you and then you can let me know if things feel clunky or whatnot
I am hoping to get a nice and friendly api
I got a new build coming some with some nice things, i'll push that too
in glsl
it just gets stripped from the final glsl
they seem to have out and inout in the final compilation...
but interestingly not on the input...
seems inout is mostly used in the main method