the quality of the stroke is a bit too low

[Wladefant]

I can clearly see the pixels of the stroke, that gives it a very cheap look.
For comparison of strokes of teh same size

js draw:

and samsung ntoes:

[personalizedrefrigerator]

There are a few things that could be causing this:

1. Not scaling the canvas area by the device-pixel ratio

If the stroke was just drawn and the canvas hasn't been moved (and you're on a high resolution display), js-draw probably isn't correctly scaling the canvas.

If this is the case, I'm hopeful that this will be easy to fix. It may make js-draw slower though.

2. js-draw's rendering cache

If you aren't on a high resolution display, and the canvas was moved after the stroke was first drawn, it could be js-draw's internal cache. It does require a large-ish number of strokes to activate the cache (so this would only be the case if there are a large number of strokes just off-screen).

js-draw internally uses a 2-d tree to divide the drawing area into smaller canvases. This allows js-draw to avoid potentially expensive re-renders of parts of the screen with many strokes.

With the goal of avoiding re-renders, the cache currently allows the tree's canvases to be scaled up by 1.3×, at some zoom levels, this leads to blurriness, and at other zoom levels (when the cache nodes aren't being scaled up), this is fine.

[Wladefant]

I am on a high resolution screen (Samsung Galaxy tab s8+). Not many strokes

[personalizedrefrigerator]

Incorrect canvas scaling should be addressed by this commit.

[personalizedrefrigerator]

It's in the latest prerelease: https://github.com/personalizedrefrigerator/joplin/releases/tag/prerelease-2

Note that this prerelease also fixes a rather significant sync issue. The issue should only affect users who previously had the second-latest prerelase installed, and only the images edited with that prerelease.

[Wladefant]

Yes sync issue, Just wanted to report it

[Wladefant]

The Quality is much better now, but when zooming out it gets a bit like it is too low quality. But bear in mind please, if something affects latency dont add it, because latency is priority number one and it still definitely lacks behind samsungs latency though I am not sure it is possible to achieve this, as we are based on react native

Screen_Recording_20231031_103023_Joplin.Beta.mp4

[personalizedrefrigerator]

That is probably because of the cache (see explanation above).

You can see whether the cache is being, or has been, used by clicking on "About" under the "Page" menu, then clicking "developer information":

Above, the developer information menu states that 90/90 cache records have been used. This means that the cache has been used since the image has been opened.

I'm hopeful that this can be improved without degrading performance (perhaps by fixing cache-related performance issues elsewhere :) ).