You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to implement the following tutorials - https://github.com/mizrael/BlazorCanvas using blazor server side. But already on example nr.2 I see how any object is drawn on canvas is flickering.
I've made a test and created a separate solution with the same code, but instead using blazor wasm - no flickering at all.
That's the problem with blazor server?
The text was updated successfully, but these errors were encountered:
hi @Bobetti , is there a particular reason why you want to use Blazor Server? All the calls to the HTML Context happen on the client-side, so I can think that flickering might be due to occasional calls to the backend which inevitably slow down the app.
If you definitely need to communicate with a server, I would suggest to expose an API (possibly with a fast transport like gRPC) and call it only when really necessary. Keep also in mind that Blazor WASM is single-threaded (for now) so any call will block the rendering.
Thing is, I'm writing a project management software using Blazor-server. As a small part of my service, I want to implement a whiteboard functionality for the image feedback process. Images are loaded from Azure blobs and clients can draw any comments on them.
Starting doing tutorials from the above post, I noticed, that even such a simple thing as - show an image on canvas - not suitable for Blazor-server, image is flickering all the time.
I'm trying to implement the following tutorials - https://github.com/mizrael/BlazorCanvas using blazor server side. But already on example nr.2 I see how any object is drawn on canvas is flickering.
I've made a test and created a separate solution with the same code, but instead using blazor wasm - no flickering at all.
That's the problem with blazor server?
The text was updated successfully, but these errors were encountered: