Better Scribble-to-Erase

Open
#187 8 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
kotlin
Domain
desktop

Research direction

Start by reading the scribble-to-erase implementation and its related tests to find how strokes are selected for removal; the issue does not name specific files or tests. Compare the current stroke-touch behavior with an option that erases within a bounding box around the scribble, and consider the reported tiny leftover dots when defining expected results.

Written by the indexing model from the issue text.

Description

I'm an avid scribble-to-erase user, however it seems like it erases every stroke the scribble stroke touches, rather than the area the scribble covers, often leading to tiny dots left over. Could there be an option to erase everything in a bounding box surrounding the scribble, rather than only what the stroke touches?

Dominant language
Kotlin
Stars
269
Forks
44
Avg merge
1d 17h
Merged PRs (30d)
22

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Ethran/notable

All issues in Ethran/notable

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.