Add drawingPrecision to API
See original GitHub issueThe current setting is too easy, drawing outside the stroke is still too easy to be correct.
Could be good idea to add a variable for precision.
drawingPrecision
: number, default 1. The ratio of width of the “shadow stroke” to draw in in order to be correct, 0.5 is “all pen’s stroke should be within the character’s strokes”.
Something like that.
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
ApplicationSettings.FreeformDrawingPrecision property (Visio)
... shows how to use the FreeformDrawingPrecision property to print the current freeform drawing precision setting in the Immediate window.
Read more >Increase point drawing precision - python - Stack Overflow
The problem comes from the resoltion of 100 dpi. Since the dots' positions need to be multiples of 1 pixel, their positions look...
Read more >What's New - Onshape
... REST API: Add face color, hidden state and type of composite to body ... Fixed an issue with drawing precision not matching...
Read more >Bringing The OS Data Hub To Desktop GIS | Blog
Add overlay wizard OS data hub API screenshot In order to access any of ... This simplicity, and drawing precision, is serendipity at...
Read more >pixel/imdraw.go at master · faiface/pixel - GitHub
with a nice immediate-mode-like API. package imdraw. import ( ... Precision - curve drawing precision, only applies to circles and ellipses ... Add(b.col)....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
added a
leniency
param in 0.9.0 which allows controlling how strict grading is.Yeah, this is definitely an issue. I’ll work on improving matching this weekend. It might even make sense to automatically be more strict with matching depending on the stroke number, or depending on if the outline is visible too. For example if there’s no outline visible, it makes sense to be lenient on the position of the first stroke since users don’t necessarily know exactly where it should be drawn, but less lenient afterwards since they have a reference point. Of course, if the outline is shown already then the user shouldn’t have any confusion about where to draw the stroke.